[crypto v3 2/2] chcr: Add support for Inline IPSec

register xfrmdev_ops callbacks, Send IPsec tunneled data to HW for inline processing. The driver use hardware crypto accelerator to encrypt and generate ICV for the transmitted packet in Inline mode. Signed-off-by: Atul Gupta Signed-off-by: Harsh Jain Signed-off-by: Ganesh Goudar --- V2: Fixed

[crypto v3 1/2] cxgb4: Add support for Inline IPSec Tx

Added Tx routine for ULD - define interface for ULD Tx. Export routines used for Tx data - Routines common for data transmit are used by cxgb4 and chcr drivers. - EXPORT routines enable transmit from chcr driver. Signed-off-by: Atul Gupta Signed-off-by: Ganesh Goudar --- V2: Fixed the build w

[PATCH] net/smc: Fix preinitialization of buf_desc in __smc_buf_create()

With gcc-4.1.2: net/smc/smc_core.c: In function ‘__smc_buf_create’: net/smc/smc_core.c:567: warning: ‘bufsize’ may be used uninitialized in this function Indeed, if the for-loop is never executed, bufsize is used uninitialized. In addition, buf_desc is stored for later use, while it is

Re: question lan9303: DSA concurrency and locking,

On 15. nov. 2017 15:08, Andrew Lunn wrote: On Wed, Nov 15, 2017 at 01:08:22PM +0100, Egil Hjelmeland wrote: Hi experts Hi, thanks for response, both Andrew and Vivien! I am hoping for some guidance. Does DSA offer any protection against concurrent calls of dsa_switch_ops? Hi Egil DSA it

Re: [PATCH 26/31] nds32: Build infrastructure

On Thu, Nov 16, 2017 at 11:03 AM, Greentime Hu wrote: > 2017-11-13 18:45 GMT+08:00 Geert Uytterhoeven : >> Given the checks for __NDS32_EB__, NDS32 can be either big or little endian, >> so you should have (excatly one of) CPU_BIG_ENDIAN or CPU_LITTLE_ENDIAN set. > > Thanks. > I will check if we n

Re: [PATCH 26/31] nds32: Build infrastructure

2017-11-13 18:45 GMT+08:00 Geert Uytterhoeven : > On Wed, Nov 8, 2017 at 11:16 AM, Arnd Bergmann wrote: >> On Wed, Nov 8, 2017 at 6:55 AM, Greentime Hu wrote: >>> --- /dev/null >>> +++ b/arch/nds32/Kconfig >>> @@ -0,0 +1,107 @@ >>> +# >>> +# For a description of the syntax of this configuration f

pull request (net): ipsec 2017-11-16

1) Copy policy family in clone_policy, otherwise this can trigger a BUG_ON in af_key. From Herbert Xu. 2) Revert "xfrm: Fix stack-out-of-bounds read in xfrm_state_find." This added a regression with transport mode when no addresses are configured on the policy template. Both patches are

[PATCH 1/2] xfrm: Copy policy family in clone_policy

From: Herbert Xu The syzbot found an ancient bug in the IPsec code. When we cloned a socket policy (for example, for a child TCP socket derived from a listening socket), we did not copy the family field. This results in a live policy with a zero family field. This triggers a BUG_ON check in th

[PATCH 2/2] Revert "xfrm: Fix stack-out-of-bounds read in xfrm_state_find."

This reverts commit c9f3f813d462c72dbe412cee6a5cbacf13c4ad5e. This commit breaks transport mode when the policy template has widlcard addresses configured, so revert it. Signed-off-by: Steffen Klassert --- net/xfrm/xfrm_policy.c | 29 ++--- 1 file changed, 18 insertions(

Re: [PATCH] net: bridge: add max_fdb_count

Hi Sarah, On Thu, Nov 16, 2017 at 01:20:18AM -0800, Sarah Newman wrote: > I note that anyone who would run up against a too-low limit on the maximum > number of fdb entries would also be savvy enough to fix it in a matter of > minutes. I disagree on this point. There's a huge difference between e

Re: [RFC] [PATCH] netns: Fix race in virtual interface bringup

Le 15/11/2017 à 20:04, Dan Rue a écrit : > Adding CC netdev > > Can someone comment on the expected behavior of this test case? > > Here's the isolated test: > > ip netns del tst_net_ns0 > ip netns del tst_net_ns1 > ip netns add tst_net_ns0 > ip netns add tst_net_ns1 > ip net

Re: [PATCH RfC 1/2] net: phy: core: remove now uneeded disabling of interrupts

On 15 November 2017 at 22:19, Heiner Kallweit wrote: > Am 15.11.2017 um 23:04 schrieb Florian Fainelli: >> On 11/12/2017 01:08 PM, Heiner Kallweit wrote: >>> After commits c974bdbc3e "net: phy: Use threaded IRQ, to allow IRQ from >>> sleeping devices" and 664fcf123a30 "net: phy: Threaded interrupt

Re: [PATCH] net: bridge: add max_fdb_count

On 16/11/17 11:20, Sarah Newman wrote: > On 11/15/2017 11:31 PM, Nikolay Aleksandrov wrote: >> On 15/11/17 21:27, Sarah Newman wrote: >>> Current memory and CPU usage for managing bridge fdb entries is unbounded. >>> Add a parameter max_fdb_count, controlled from sysfs, which places an upper >>> li

Re: [PATCH] net: bridge: add max_fdb_count

On 11/15/2017 11:31 PM, Nikolay Aleksandrov wrote: > On 15/11/17 21:27, Sarah Newman wrote: >> Current memory and CPU usage for managing bridge fdb entries is unbounded. >> Add a parameter max_fdb_count, controlled from sysfs, which places an upper >> limit on the number of entries. Defaults to 102

Re: [RFC PATCH net-next 0/2] Configuring PFC stall prevention via ethtool

On Thu, Nov 16, 2017 at 4:44 AM, Andrew Lunn wrote: >> What do other vendors support? Time? Number of pause frames sent? > > So i checked a few Marvell Switches. You can also specify a time. It > is a little bit more complex than that, since the units of time depend > on the link speed. But conver

Re: [PATCH] net: Convert net_mutex into rw_semaphore and down read it on net->init/->exit

On 15.11.2017 19:29, Eric W. Biederman wrote: > Kirill Tkhai writes: > >> On 15.11.2017 09:25, Eric W. Biederman wrote: >>> Kirill Tkhai writes: >>> Curently mutex is used to protect pernet operations list. It makes cleanup_net() to execute ->exit methods of the same operations set, >>

Re: [RFC PATCH net-next 0/2] Configuring PFC stall prevention via ethtool

On Wed, Nov 15, 2017 at 09:00:09PM +0200, Eran Ben Elisha wrote: > From: Inbar Karmy > > This RFC adds support for configuring PFC stall prevention through ethtool. > > In the event where the device unexpectedly becomes unresponsive for a long > period of time, flow control mechanism may propaga

Re: [RFC PATCH 00/14] Introducing AF_PACKET V4 support

On Thu, 16 Nov 2017 08:09:04 +0100 Björn Töpel wrote: > Ideally, it would be best not having to introduce yet another xmit > ndo. I believe ndo_xdp_xmit/ndo_xdp_flush would be the best fit, but > we need to extend it with a destructor callback and potentially some > kind of DMA trait. Why DMA? F

Re: [PATCH net v5 1/2] ARM: dts: imx: name the interrupts for the fec ethernet driver

On Fri, Nov 03, 2017 at 10:29:58AM -0700, Troy Kisky wrote: > imx7s/imx7d has the ptp interrupt newly added as well. > > For imx7, "int0" is the interrupt for queue 0 and ENET_MII > "int1" is for queue 1 > "int2" is for queue 2 > > For imx6sx, "int0" handles all 3 queues and ENET_MII > > And of

[PATCH v4] wcn36xx: Set default BTLE coexistence config

From: Eyal Ilsar If the value for the firmware configuration parameters BTC_STATIC_LEN_LE_BT and BTC_STATIC_LEN_LE_WLAN are not set the duty cycle between BT and WLAN is such that if BT (including BLE) is active WLAN gets 0 bandwidth. When tuning these parameters having a too high value for WLAN

Re: [RFC PATCH 00/14] Introducing AF_PACKET V4 support (AF_XDP or AF_CHANNEL?)

On Tue, 14 Nov 2017 20:01:01 +0100 Björn Töpel wrote: > 2017-11-14 18:19 GMT+01:00 Jesper Dangaard Brouer : > > > > On Mon, 13 Nov 2017 22:07:47 +0900 Björn Töpel > > wrote: > > > >> I'll summarize the major points, that we'll address in the next RFC > >> below. > >> > >> * Instead of extend

[PATCH v2] mwl8k: Expand non-DFS 5G channels

Add non-DFS 5G upper channels (149-165) besides existed 4 lower channels (36, 40, 44, 48). { .band = NL80211_BAND_5GHZ, .center_freq = 5745, .hw_value = 149, }, { .band = NL80211_BAND_5GHZ, .center_freq = 5765, .hw_value = 153, }, { .band = NL80211_BAND_5GHZ, .center_freq = 5785, .hw_value = 157, }

<    1   2