[PATCH net-next] cxgb4: Reset dcb state machine and tx queue prio only if dcb is enabled

When cxgb4 is enabled with CONFIG_CHELSIO_T4_DCB set, VI enable command gets called with DCB enabled. But when we have a back to back setup with DCB enabled on one side and non-DCB on the Peer side. Firmware doesn't send any DCB_L2_CFG, and DCB priority is never set for Tx queue. But driver resets

[PATCH net 1/1] qede: prevent chip hang when increasing channels

qede requires qed to provide enough resources to accommodate 16 combined channels, but that upper-bound isn't actually being enforced by it. Instead, qed inform back to qede how many channels can be opened based on available resources - but that calculation doesn't really take into account the

[PATCH net-next 0/2] net: l3mdev: Allow send on enslaved interface

First patch preps for the second. The second is required for several use cases such as ping on an interface and BFD that need to send packets on a specific interface, including ones enslaved to a VRF device. David Ahern (2): net: l3mdev: Move get_saddr and rt6_dst net: l3mdev: Allow send on

[PATCH net-next 2/2] net: l3mdev: Allow send on enslaved interface

Allow udp and raw sockets to send by oif that is an enslaved interface versus the l3mdev/VRF device. For example, this allows BFD to use ifindex from IP_PKTINFO on a receive to send a response without the need to convert to the VRF index. It also allows ping and ping6 to work when specifying an

[PATCH net-next 1/2] net: l3mdev: Move get_saddr and rt6_dst

Move l3mdev_rt6_dst_by_oif and l3mdev_get_saddr to l3mdev.c. Collapse l3mdev_get_rt6_dst into l3mdev_rt6_dst_by_oif since it is the only user and keep the l3mdev_get_rt6_dst name for consistency with other hooks. A follow-on patch adds more code to these functions making them long for inlined

[PATCH net-next v2] net: vrf: Create FIB tables on link create

Tables have to exist for VRFs to function. Ensure they exist when VRF device is created. Signed-off-by: David Ahern --- v2 - create table before rt6 allocation per comment from DaveM drivers/net/vrf.c | 13 +++-- net/ipv4/fib_frontend.c | 1 +

Re: [PATCH net-next] net: vrf: Create FIB tables on link create

On 5/4/16 10:24 PM, David Miller wrote: From: David Ahern Date: Wed, 4 May 2016 21:18:07 -0700 @@ -372,9 +372,13 @@ static int vrf_rt6_create(struct net_device *dev) if (!rt6) goto out; - rt6->dst.output = vrf_output6; -

Re: [PATCH net-next] tcp: two more missing bh disable

From: Eric Dumazet Date: Wed, 04 May 2016 15:27:29 -0700 > From: Eric Dumazet > > percpu_counter only have protection against preemption. > > TCP stack uses them possibly from BH, so we need BH protection > in contexts that could be run in process

[PATCH] net: ipv6: tcp reset, icmp need to consider L3 domain

Responses for packets to unused ports are getting lost with L3 domains. IPv4 has ip_send_unicast_reply for sending TCP responses which accounts for L3 domains; update the IPv6 counterpart tcp_v6_send_response. For icmp the L3 master check needs to be moved up in icmp6_send to properly respond to

Re: [net-next] MAINTAINERS: Cleanup Intel Wired LAN maintainers list

From: Jeff Kirsher Date: Wed, 4 May 2016 15:49:39 -0700 > With the recent "retirements" and other changes, make the maintainers > list a lot less confusing and a bit more straight forward. > > Signed-off-by: Jeff Kirsher > Acked-by:

Re: [PATCH net-next] net: vrf: Create FIB tables on link create

From: David Ahern Date: Wed, 4 May 2016 21:18:07 -0700 > @@ -372,9 +372,13 @@ static int vrf_rt6_create(struct net_device *dev) > if (!rt6) > goto out; > > - rt6->dst.output = vrf_output6; > - rt6->rt6i_table = fib6_get_table(net,

[PATCH net-next] net: vrf: Create FIB tables on link create

Tables have to exist for VRFs to function. Ensure they exist when VRF device is created. Signed-off-by: David Ahern --- drivers/net/vrf.c | 11 +-- net/ipv4/fib_frontend.c | 1 + net/ipv6/ip6_fib.c | 1 + 3 files changed, 11 insertions(+), 2

Re: [PATCH net-next 00/13] net: Various VRF patches

On 5/4/16 9:59 PM, David Miller wrote: From: David Ahern Date: Wed, 4 May 2016 20:33:17 -0700 Various fixes and features for VRF over the past few months. I really dislike a patch series that is simply a hodge podge of unrelated things. Please group your changes

Re: [PATCH net-next 00/13] net: Various VRF patches

From: David Ahern Date: Wed, 4 May 2016 20:33:17 -0700 > Various fixes and features for VRF over the past few months. I really dislike a patch series that is simply a hodge podge of unrelated things. Please group your changes into logical bunches, and submit them as

Re: [net-next 08/15] i40e: Allow user to change input set mask for flow director

From: "Patil, Kiran" Date: Wed, 4 May 2016 19:47:26 -0700 > This is not new feature implemented in i40e driver. This is the > original feature of ethtool which allows user to specify subset of > tuple for setting up flow director. Where is the interpretation of this

Re: [PATCH net-next v2] macvtap: add namespace support to the sysfs device class

From: Marc Angel Date: Thu, 5 May 2016 01:33:09 +0100 > On Wed, May 4, 2016 at 9:04 PM, David Miller wrote: >> From: Marc Angel >> Date: Tue, 3 May 2016 20:30:54 +0200 >> >>> @@ -1274,6 +1285,7 @@ static int macvtap_device_event(struct

Re: [net-next 08/15] i40e: Allow user to change input set mask for flow director

On Tue, Apr 26, 2016 at 1:55 PM, Jeff Kirsher wrote: > From: Kiran Patil > > This patch implements feature, which allows user to change > input set mask for flow director using side-band channel. > This patch adds definition of FLOW_TYPE_MASK

Re: task_diag: add a new interface to get information about processes

On May 4, 2016 7:14 PM, "Stephen Hemminger" wrote: > > On Wed, 4 May 2016 15:34:21 -0700 > Andrey Vagin wrote: > > > Hi Stephen, > > > > On Wed, May 4, 2016 at 1:22 PM, Stephen Hemminger > > wrote: > > > I understand how

[v10, 4/7] dt: move guts devicetree doc out of powerpc directory

Move guts devicetree doc to Documentation/devicetree/bindings/soc/fsl/ since it's used by not only PowerPC but also ARM. And add a specification for 'little-endian' property. Signed-off-by: Yangbo Lu Acked-by: Scott Wood Acked-by: Rob Herring

[v10, 0/7] Fix eSDHC host version register bug

This patchset is used to fix a host version register bug in the T4240-R1.0-R2.0 eSDHC controller. To get the SoC version and revision, it's needed to add the GUTS driver to access the global utilities registers. So, the first four patches are to add the GUTS driver. The following patches except

[PATCH net-next 13/13] net: ipv6: address selection should only consider devices in L3 domain

IPv6 version of 3f2fb9a834cb ("net: l3mdev: address selection should only consider devices in L3 domain"). IPv4's follow up commit, a17b693cdd876 ("net: l3mdev: prefer VRF master for source address selection"), is not relevant. For IPv6 the VRF device should not be preferred over the dst_dev as it

[PATCH net-next 12/13] net: vrf: Implement get_saddr for IPv6

Right now source address selection is all screwed up for a number of use cases. It does not properly take into account VRF centric addresses or even valid routes for a VRF. Fix by implementating a get_saddr method similar to what was done for IPv4. The get_saddr6 method does a full lookup which

[PATCH net-next 07/13] net: vrf: ipv4 support for local traffic to local addresses

Add support for locally originated traffic to VRF local addresses. This patch handles IPv4 support; follow on patch handles IPv6. With this patch, ping, tcp and udp packets to a local IPv4 address are successfully routed: $ ping -c1 -I red 10.100.1.1 ping: Warning: source address might

[PATCH net-next 03/13] net: l3mdev: Allow send on enslaved interface

Allow udp and raw sockets to send by oif that is an enslaved interface versus the l3mdev/VRF device. For example, this allows BFD to use ifindex from IP_PKTINFO on a receive to send a response without the need to convert to the VRF index. It also allows ping and ping6 to work when specifying an

[PATCH net-next 11/13] net: vrf: rcu protect changes to private data

The problem is that one cpu is processing packets which includes using the cached route entries in the vrf device's private data and on another cpu the device is getting deleted which releases the routes and sets the pointers to NULL. Fix by rcu protecting the changes. Signed-off-by: David Ahern

[PATCH net-next 01/13] net: vrf: Create FIB tables on link create

Tables have to exist for VRFs to function. Ensure they exist when VRF device is created. Signed-off-by: David Ahern --- drivers/net/vrf.c | 11 +-- net/ipv4/fib_frontend.c | 1 + net/ipv6/ip6_fib.c | 1 + 3 files changed, 11 insertions(+), 2

[PATCH net-next 10/13] net: vrf: Handle ipv6 multicast and link-local addresses

IPv6 multicast and link-local addresses require special handling by the VRF driver. Rather than using the VRF device index and a full FIB lookups packets to/from these addresses should use direct FIB lookups. Multicast routes do not make sense for L3 master devices. So, do not add mcast routes

[PATCH net-next 09/13] net: l3mdev: Propagate route lookup flags for IPv6

Commit 6f21c96a78b8 ("ipv6: enforce flowi6_oif usage in ip6_dst_lookup_tail") converted ip6_route_output to ip6_route_output_flags which takes a flags input parameter. That arg should be passed to l3mdev_get_rt6_dst for it to use in lookups as well. Needed by the next patch Signed-off-by: David

[PATCH net-next 08/13] net: vrf: ipv6 support for local traffic to local addresses

Add support for locally originated traffic to VRF-local addresses. This patch handles IPv6 support. With this patch, ping, tcp and udp packets to a local IPv6 address are successfully routed: $ ping6 -c1 -I red 2100:1::1 ping6: Warning: source address might be selected on device other

[PATCH net-next 06/13] net: original ingress device index in PKTINFO

Applications such as OSPF and BFD need the original ingress device not the VRF device; the latter can be derived from the former. To that end add the skb_iif to inet_skb_parm and set it in ipv4 code after clearing the skb control buffer similar to IPv6. From there the pktinfo can just pull it from

[PATCH net-next 02/13] net: l3mdev: Move get_saddr and rt6_dst

Move l3mdev_rt6_dst_by_oif and l3mdev_get_saddr to l3mdev.c. Collapse l3mdev_get_rt6_dst into l3mdev_rt6_dst_by_oif since it is the only user and keep the l3mdev_get_rt6_dst name for consistency with other hooks. A follow-on patch adds more code to these functions making them long for inlined

[PATCH net-next 04/13] net: ipv6: tcp reset, icmp need to consider L3 domain

Responses for packets to unused ports are getting lost with L3 domains. IPv4 has ip_send_unicast_reply for sending TCP responses which accounts for L3 domains; update the IPv6 counterpart tcp_v6_send_response. For icmp the L3 master check needs to be moved up in icmp6_send to properly respond to

[PATCH net-next 05/13] net: l3mdev: Add hook in ip and ipv6

Currently the VRF driver uses the rx_handler to switch the skb device to the VRF device. Switching the dev prior to the ip / ipv6 layer means the VRF driver has to duplicate IP/IPv6 processing which is just overhead and makes features such as retaining the ingress device index more complicated

[PATCH net-next 00/13] net: Various VRF patches

Various fixes and features for VRF over the past few months. Patch 1 creates the FIB tables when VRF device is created. Patch 2 is a prep for 3 which allow sends via cmsg/IP-PKTINFO on interfaces enslaved to a VRF device. Patch 4 fixes missing TCP reset / ECONNREFUSED packets in response to

Re: [PATCH net-next 14/14] ip4ip6: Support for GSO/GRO

On Wed, May 4, 2016 at 6:20 PM, Eric Dumazet wrote: > On Wed, 2016-05-04 at 18:02 -0700, Tom Herbert wrote: >> Signed-off-by: Tom Herbert >> --- >> diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h >> index 928b456..6a811fa 100644 >> ---

[v10, 2/7] ARM64: dts: ls2080a: add device configuration node

Add the dts node for device configuration unit that provides general purpose configuration and status for the device. Signed-off-by: Yangbo Lu Acked-by: Scott Wood --- Changes for v5: - Added this patch Changes for v6: - None Changes for v7:

[v10, 1/7] Documentation: DT: update Freescale DCFG compatible

Update Freescale DCFG compatible with 'fsl,-dcfg' instead of 'fsl,ls1021a-dcfg' to include more chips such as ls1021a, ls1043a, and ls2080a. Signed-off-by: Yangbo Lu --- Changes for v8: - Added this patch Changes for v9: - Added a list for the possible

[v10, 6/7] MAINTAINERS: add entry for Freescale SoC drivers

Add maintainer entry for Freescale SoC drivers including the QE library and the GUTS driver now. Also add maintainer for QE library. Signed-off-by: Yangbo Lu Acked-by: Scott Wood Acked-by: Qiang Zhao --- Changes for v8: - Added

[v10, 3/7] soc: fsl: add GUTS driver for QorIQ platforms

The global utilities block controls power management, I/O device enabling, power-onreset(POR) configuration monitoring, alternate function selection for multiplexed signals,and clock control. This patch adds GUTS driver to manage and access global utilities block. Signed-off-by: Yangbo Lu

[v10, 7/7] mmc: sdhci-of-esdhc: fix host version for T4240-R1.0-R2.0

The eSDHC of T4240-R1.0-R2.0 has incorrect vender version and spec version. Acturally the right version numbers should be VVN=0x13 and SVN = 0x1. This patch adds the GUTS driver support for eSDHC driver to get SVR(System version register). And fix host version to avoid that incorrect version

[v10, 5/7] powerpc/fsl: move mpc85xx.h to include/linux/fsl

Move mpc85xx.h to include/linux/fsl and rename it to svr.h as a common header file. It has been used for mpc85xx and it will be used for ARM-based SoC as well. Signed-off-by: Yangbo Lu Acked-by: Wolfram Sang Acked-by: Stephen Boyd

Re: [net-next 08/15] i40e: Allow user to change input set mask for flow director

On 16-05-04 07:47 PM, Patil, Kiran wrote: > On 4/26/2016 8:48 PM, David Miller wrote: >> From: Jeff Kirsher >> Date: Tue, 26 Apr 2016 13:55:41 -0700 >> >>> From: Kiran Patil >>> >>> This patch implements feature, which allows user to change >>>

RE: [v9, 6/7] MAINTAINERS: add entry for Freescale SoC driver

Thanks a lot, Scott and Qiang. Will change 'DRIVER' to 'DRIVERS' and update the patchset with your acts. Best regards, Yangbo Lu > -Original Message- > From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc- > ow...@vger.kernel.org] On Behalf Of Scott Wood > Sent: Thursday, May 05,

RE: [v9, 6/7] MAINTAINERS: add entry for Freescale SoC driver

On Wed, 2016-05-04 at 11:24 +0800, Yangbo Lu wrote: > -Original Message- > From: Yangbo Lu [mailto:yangbo...@nxp.com] > Sent: Wednesday, May 04, 2016 11:25 AM > To: linux-...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; > devicet...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;

Re: [PATCH net-next 01/14] gso: Remove arbitrary checks for unsupported GSO

On Wed, May 4, 2016 at 6:02 PM, Tom Herbert wrote: > In several gso_segment functions there are checks of gso_type against > a seemingly abitrary list of SKB_GSO_* flags. This seems like an > attempt to identify unsupported GSO types, but since the stack is > the one that

Re: [net-next 08/15] i40e: Allow user to change input set mask for flow director

On 4/26/2016 8:48 PM, David Miller wrote: From: Jeff Kirsher Date: Tue, 26 Apr 2016 13:55:41 -0700 From: Kiran Patil This patch implements feature, which allows user to change input set mask for flow director using side-band channel. This

Re: [PATCH net-next 03/14] udp: Don't set skb->encapsulation with RCO

On Wed, May 4, 2016 at 6:02 PM, Tom Herbert wrote: > When RCO is in effect we want to ensure that the outer checksum is > properly offloaded. Don't set skb->encapsulation in this case to > ensure that checksum offload is later considered for hw_features > instead of

Re: task_diag: add a new interface to get information about processes

On Wed, 4 May 2016 15:34:21 -0700 Andrey Vagin wrote: > Hi Stephen, > > On Wed, May 4, 2016 at 1:22 PM, Stephen Hemminger > wrote: > > I understand how reading /proc or /sys can be a bottleneck, but this > > proposed method using a system call is

Re: [PATCH net-next 14/14] ip4ip6: Support for GSO/GRO

On Wed, 2016-05-04 at 18:02 -0700, Tom Herbert wrote: > Signed-off-by: Tom Herbert > --- > diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h > index 928b456..6a811fa 100644 > --- a/include/linux/skbuff.h > +++ b/include/linux/skbuff.h > @@ -484,6 +484,8 @@ enum {

[PATCH net-next 06/14] fou: Add encap ops for IPv6 tunnels

Thsi packet adds IP tunnel encapsulation operations for IPv6. This includes the infrastructure to add and delete operations. IPv6 variants for fou6_build_header and gue6_build_header are added in a new fou6 module. These encapsulation operations for fou and gue are automatically added when the

[PATCH net-next 13/14] ip6ip6: Support for GSO/GRO

Signed-off-by: Tom Herbert --- include/linux/netdev_features.h | 5 - include/linux/netdevice.h | 1 + include/linux/skbuff.h | 2 ++ net/core/ethtool.c | 1 + net/ipv6/ip6_offload.c | 27 +++

[PATCH net-next 10/14] ip6_tun: Add infrastructure for doing encapsulation

Add encap_hlen and ip_tunnel_encap structure to ip6_tnl. Add functions for getting encap hlen, setting up encap on a tunnel, performing encapsulation operation. Signed-off-by: Tom Herbert --- include/net/ip6_tunnel.h | 8 +- net/ipv6/ip6_tunnel.c | 4 +++

[PATCH net-next 05/14] fou: Split out {fou,gue}_build_header

Create __fou_build_header and __gue_build_header. These implement the protocol generic parts of building the fou and gue header. fou_build_header and gue_build_header implement the IPv4 specific functions and call the __*_build_header functions. Signed-off-by: Tom Herbert

[PATCH net-next 01/14] gso: Remove arbitrary checks for unsupported GSO

In several gso_segment functions there are checks of gso_type against a seemingly abitrary list of SKB_GSO_* flags. This seems like an attempt to identify unsupported GSO types, but since the stack is the one that set these GSO types in the first place this seems unnecessary to do. If a

[PATCH net-next 11/14] ip6_gre: Add support for fou/gue encapsulation

Add netlink and setup for encapsulation Signed-off-by: Tom Herbert --- net/ipv6/ip6_gre.c | 75 ++ 1 file changed, 75 insertions(+) diff --git a/net/ipv6/ip6_gre.c b/net/ipv6/ip6_gre.c index c827ae8..2beb212 100644 ---

[PATCH net-next 12/14] ip6_tunnel: Add support for fou/gue encapsulation

Add netlink and setup for encapsulation Signed-off-by: Tom Herbert --- net/ipv6/ip6_tunnel.c | 89 +++ 1 file changed, 83 insertions(+), 6 deletions(-) diff --git a/net/ipv6/ip6_tunnel.c b/net/ipv6/ip6_tunnel.c index

[PATCH net-next 02/14] gre6: Fix flag translations

GRE for IPv6 does not properly translate for GRE flags to tunnel flags and vice versa. This patch fixes that. Signed-off-by: Tom Herbert --- net/ipv6/ip6_gre.c | 20 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/net/ipv6/ip6_gre.c

[PATCH net-next 08/14] ipv6: Change "final" protocol processing for encapsulation

When performing foo-over-UDP, UDP are receveived processed by the encapsulation header which returns another protocol to process. This may result in processing two (or more) protocols in the loop that are marked as INET6_PROTO_FINAL. The actions taken for hitting a final protocol, in particular

[PATCH net-next 09/14] fou: Support IPv6 in fou

This patch adds receive path support for IPv6 with fou. - Add address family to fou structure for open sockets. This supports AF_INET and AF_INET6. Lookups for fou ports are performed on both the port number and family. - In fou and gue receive adjust tot_len in IPv4 header or payload_len

[PATCH net-next 03/14] udp: Don't set skb->encapsulation with RCO

When RCO is in effect we want to ensure that the outer checksum is properly offloaded. Don't set skb->encapsulation in this case to ensure that checksum offload is later considered for hw_features instead of hw_enc_features. Signed-off-by: Tom Herbert ---

[PATCH net-next 04/14] fou: Call setup_udp_tunnel_sock

Use helper function to set up UDP tunnel related information for a fou socket. Signed-off-by: Tom Herbert --- net/ipv4/fou.c | 50 -- 1 file changed, 16 insertions(+), 34 deletions(-) diff --git a/net/ipv4/fou.c

[PATCH net-next 07/14] ipv6: Fix nexthdr for reinjection

In ip6_input_finish the protocol handle returns a value greater than zero the packet needs to be resubmitted using the returned protocol. The returned protocol is being ignored and each time through resubmit nexthdr is taken from an offest in the packet. This patch fixes that so that nexthdr is

[PATCH net-next 00/14] ipv6: Enable GUEoIPv6 and more fixes for v6 tunneling

This patch set: - Fixes GRE6 to process translate flags correctly from configuration - Adds support for GSO and GRO for ip6ip6 and ip4ip6 - Add support for FOU and GUE in IPv6 - Support GRE, ip6ip6 and ip4ip6 over FOU/GUE - Fixes ip6_input to deal with UDP encapsulations - Some other

[PATCH net-next 14/14] ip4ip6: Support for GSO/GRO

Signed-off-by: Tom Herbert --- include/linux/netdev_features.h | 5 - include/linux/netdevice.h | 1 + include/linux/skbuff.h | 2 ++ include/net/inet_common.h | 5 + net/ipv4/af_inet.c | 12 +++- net/ipv6/ip6_offload.c

Re: [PATCH net-next v2] macvtap: add namespace support to the sysfs device class

On Wed, May 4, 2016 at 9:04 PM, David Miller wrote: > From: Marc Angel > Date: Tue, 3 May 2016 20:30:54 +0200 > >> @@ -1274,6 +1285,7 @@ static int macvtap_device_event(struct notifier_block >> *unused, >> unsigned long event,

[PATCH net-next v3] macvtap: add namespace support to the sysfs device class

When creating macvtaps that are expected to have the same ifindex in different network namespaces, only the first one will succeed. The others will fail with a sysfs_warn_dup warning due to them trying to create the following sysfs link (with 'NN' the ifindex of macvtapX):

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: net/core/rtnetlink.c between commit: 5f8e44741f9f ("net: fix infoleak in rtnetlink") from the net tree and commit: 270cb4d05b29 ("rtnl: align nlattr properly when needed") from the net-next tree. I fixed it up

Re: [Y2038] [RESEND PATCH 2/3] fs: poll/select/recvmmsg: use timespec64 for timeout events

On Wed, May 4, 2016 at 4:51 PM, Andrew Morton wrote: > On Wed, 04 May 2016 23:08:11 +0200 Arnd Bergmann wrote: > >> > But I'm less comfortable making the call on this one. It looks >> > relatively straight forward, but it would be good to have maintainer

[PATCH net-next] cnic: call cp->stop_hw() in cnic_start_hw() on allocation failure

We recently had a system crash in the cnic module. Vmcore analysis confirmed that "ip link up" was executed which failed due to an allocation failure because of memory fragmentation. Futher analysis revealed that the cnic irq vector was still allocated after the "ip link up" that failed. When

Re: [Y2038] [RESEND PATCH 2/3] fs: poll/select/recvmmsg: use timespec64 for timeout events

On Wed, 04 May 2016 23:08:11 +0200 Arnd Bergmann wrote: > > But I'm less comfortable making the call on this one. It looks > > relatively straight forward, but it would be good to have maintainer > > acks before I add it to my tree. > > Agreed. Feel free to add my > >

Re: [REGRESSION] asix: Lots of asix_rx_fixup() errors and slow transmissions

On Tue, May 3, 2016 at 3:54 AM, Dean Jenkins wrote: > On 03/05/16 11:04, Guodong Xu wrote: >> >> did you test on ARM 64-bit system or ARM 32-bit? I ask because HiKey >> is an ARM 64-bit system. I suggest we should be careful on that. I saw >> similar issues when

Re: [Y2038] [RESEND PATCH 2/3] fs: poll/select/recvmmsg: use timespec64 for timeout events

On Wednesday 04 May 2016 13:04:37 John Stultz wrote: > On Wed, May 4, 2016 at 12:24 PM, Deepa Dinamani > wrote: > > struct timespec is not y2038 safe. > > Even though timespec might be sufficient to represent > > timeouts, use struct timespec64 here as the plan is to > >

[net-next] MAINTAINERS: Cleanup Intel Wired LAN maintainers list

With the recent "retirements" and other changes, make the maintainers list a lot less confusing and a bit more straight forward. Signed-off-by: Jeff Kirsher Acked-by: Jesse Brandeburg Acked-by: Shannon Nelson ---

[PATCH net-next] tcp: two more missing bh disable

From: Eric Dumazet percpu_counter only have protection against preemption. TCP stack uses them possibly from BH, so we need BH protection in contexts that could be run in process context Fixes: c10d9310edf5 ("tcp: do not assume TCP code is non preemptible") Signed-off-by:

Re: [PATC net-next] tcp: must block bh in __inet_twsk_hashdance()

On Wed, 2016-05-04 at 17:06 -0400, David Miller wrote: > I pushed them in by hand, they should really be there now. > > Thanks for letting me know. Thanks David Further tests show two additional missing local_bh_disable() protections around percpu_counter_dec() and one

Re: [net-next 00/14][pull request] 10GbE Intel Wired LAN Driver Updates 2016-05-04

From: Jeff Kirsher Date: Wed, 4 May 2016 09:26:34 -0700 > This series contains updates to ixgbe, ixgbevf and traffic class helpers. Pulled, thanks Jeff.

Re: [PATCH net 0/2] bnxt_en: 2 bug fixes.

From: Michael Chan Date: Wed, 4 May 2016 16:56:42 -0400 > Fix crash on ppc64 due to missing memory barrier and restore multicast > after reset. Looks good, series applied, thanks.

Re: [PATCH next] bonding: update documentation section after dev->trans_start removal

From: Florian Westphal Date: Wed, 4 May 2016 22:51:47 +0200 > Drivers that use LLTX need to update trans_start of the netdev_queue. > (Most drivers don't use LLTX; stack does this update if .ndo_start_xmit > returned TX_OK). > > Signed-off-by: Florian Westphal

Re: [PATCH next] drivers: fix dev->trans_start removal fallout

From: Florian Westphal Date: Wed, 4 May 2016 22:56:07 +0200 > kbuild test robot reported a build failure on s390. > While at it, also fix missing conversion in the tilera driver. > > Fixes: 9b36627acecd5792 ("net: remove dev->trans_start") > Reported-by: kbuild test robot

Re: [PATC net-next] tcp: must block bh in __inet_twsk_hashdance()

From: Eric Dumazet Date: Wed, 04 May 2016 11:22:11 -0700 > On Wed, 2016-05-04 at 00:54 -0400, David Miller wrote: >> From: Eric Dumazet >> Date: Tue, 03 May 2016 17:10:50 -0700 >> >> > From: Eric Dumazet >> > >> >

Re: [patch] usbnet: smsc95xx: silence an uninitialized variable warning

From: Dan Carpenter Date: Wed, 4 May 2016 09:22:01 +0300 > If the call to fn() fails then "buf" is uninitialized. Just return the > error code in that case. > > Signed-off-by: Dan Carpenter Applied. Please, in the future, use a consistent

Re: [patch] usbnet/smsc75xx: silence uninitialized variable warning

From: Dan Carpenter Date: Wed, 4 May 2016 09:21:02 +0300 > If the fn() calls fail then "buf" is uninitialized. Just return early > in that situation. > > Signed-off-by: Dan Carpenter Applied.

[PATCH net 2/2] bnxt_en: Setup multicast properly after resetting device.

The multicast/all-multicast internal flags are not properly restored after device reset. This could lead to unreliable multicast operations after an ethtool configuration change for example. Call bnxt_mc_list_updated() and setup the vnic->mask in bnxt_init_chip() to fix the issue.

[PATCH net 0/2] bnxt_en: 2 bug fixes.

Fix crash on ppc64 due to missing memory barrier and restore multicast after reset. Michael Chan (2): bnxt_en: Need memory barrier when processing the completion ring. bnxt_en: Setup multicast properly after resetting device. drivers/net/ethernet/broadcom/bnxt/bnxt.c | 23

[PATCH net 1/2] bnxt_en: Need memory barrier when processing the completion ring.

The code determines if the next ring entry is valid before proceeding further to read the rest of the entry. The CPU can re-order and read the rest of the entry first, possibly reading a stale entry, if DMA of a new entry happens right after reading it. This issue can be readily seen on a ppc64

[PATCH next] drivers: fix dev->trans_start removal fallout

kbuild test robot reported a build failure on s390. While at it, also fix missing conversion in the tilera driver. Fixes: 9b36627acecd5792 ("net: remove dev->trans_start") Reported-by: kbuild test robot Signed-off-by: Florian Westphal --- diff --git

[PATCH next] bonding: update documentation section after dev->trans_start removal

Drivers that use LLTX need to update trans_start of the netdev_queue. (Most drivers don't use LLTX; stack does this update if .ndo_start_xmit returned TX_OK). Signed-off-by: Florian Westphal --- Documentation/networking/bonding.txt | 4 ++-- 1 file changed, 2 insertions(+), 2

Re: pull request (net): ipsec 2016-05-04

From: Steffen Klassert Date: Wed, 4 May 2016 07:40:51 +0200 > 1) The flowcache can hit an OOM condition if too >many entries are in the gc_list. Fix this by >counting the entries in the gc_list and refuse >new allocations if the value is too high. > >

Re: pull request: batman-adv 20160504

From: Antonio Quartulli Date: Wed, 4 May 2016 06:23:35 +0800 > this is a pull request intended for net-next. > > In this batch you don't have any patch that depends on our fixes, > therefore you can safely merge it even if the net tree has not been > merged yet. > > In this

Re: [PATCH] fix infoleak in llc

From: Kangjie Lu Date: Tue, 3 May 2016 16:35:05 -0400 > The stack object “info” has a total size of 12 bytes. Its last byte > is padding which is not initialized and leaked via “put_cmsg”. > > Signed-off-by: Kangjie Lu Applied.

Re: [PATCH] fix infoleak in rtnetlink

From: Kangjie Lu Date: Tue, 3 May 2016 16:46:24 -0400 > The stack object “map” has a total size of 32 bytes. Its last 4 > bytes are padding generated by compiler. These padding bytes are > not initialized and sent out via “nla_put”. > > Signed-off-by: Kangjie Lu

Re: [PATCH] mdio_bus: don't return NULL from mdiobus_scan()

From: Sergei Shtylyov Date: Tue, 03 May 2016 23:14:41 +0300 > I've finally noticed that mdiobus_scan() also returns either NULL or error > value on failure. Return ERR_PTR(-ENODEV) instead of NULL since this is > the error value already filtered out by the

Re: [RESEND PATCH 2/3] fs: poll/select/recvmmsg: use timespec64 for timeout events

On Wed, May 4, 2016 at 12:24 PM, Deepa Dinamani wrote: > struct timespec is not y2038 safe. > Even though timespec might be sufficient to represent > timeouts, use struct timespec64 here as the plan is to > get rid of all timespec reference in the kernel. > > The patch

Re: [PATCH net-next v2] macvtap: add namespace support to the sysfs device class

From: Marc Angel Date: Tue, 3 May 2016 20:30:54 +0200 > @@ -1274,6 +1285,7 @@ static int macvtap_device_event(struct notifier_block > *unused, > unsigned long event, void *ptr) > { > struct net_device *dev =

[RESEND PATCH 2/3] fs: poll/select/recvmmsg: use timespec64 for timeout events

struct timespec is not y2038 safe. Even though timespec might be sufficient to represent timeouts, use struct timespec64 here as the plan is to get rid of all timespec reference in the kernel. The patch transitions the common functions: poll_select_set_timeout() and select_estimate_accuracy() to

Re: [PATC net-next] tcp: must block bh in __inet_twsk_hashdance()

On Wed, 2016-05-04 at 00:54 -0400, David Miller wrote: > From: Eric Dumazet > Date: Tue, 03 May 2016 17:10:50 -0700 > > > From: Eric Dumazet > > > > __inet_twsk_hashdance() might be called from process context, > > better block BH before acquiring

Re: pull request [net]: batman-adv 20160430

From: David Miller Date: Tue, 03 May 2016 12:33:30 -0400 (EDT) > From: Antonio Quartulli > Date: Tue, 3 May 2016 22:42:29 +0800 > >> Do you have any plan on merging net into net-next in the following days ? >> >> I am asking because I'd prefer to avoid

Re: [PATCH v2 net-next] dmfe: kill DEVICE define

From: Florian Westphal Date: Tue, 3 May 2016 18:53:15 +0200 > use net_device directly. Compile tested, objdiff shows no changes. > > Signed-off-by: Florian Westphal Applied.

Re: pull request [net]: batman-adv 20160430

On Wed, May 04, 2016 at 02:13:50PM -0400, David Miller wrote: > > Just FYI I did this last night. Thanks a lot for letting me know David. Cheers, -- Antonio Quartulli signature.asc Description: Digital signature

Re: [PATCH] tcp: ensure non-empty connection request queue

On Wed, 2016-05-04 at 11:05 -0700, Rick Jones wrote: > Assuming Peter's assertion about just drops when syncookies are not > enabled is accurate, should there be some one-time message in that case too? We have plenty of drop points in the kernel without a message in syslog, but proper SNMP

  1   2   3   >