Re: [patch net-next v2 2/4] devlink: propagate extack down to health reporter ops

2019-10-10 Thread Johannes Berg
On Thu, 2019-10-10 at 19:04 -0700, Jakub Kicinski wrote: > > if (reporter->auto_recover) > > - return devlink_health_reporter_recover(reporter, priv_ctx); > > + return devlink_health_reporter_recover(reporter, > > + priv_ctx,

Re: [patch net-next v2 2/4] devlink: propagate extack down to health reporter ops

2019-10-10 Thread Jiri Pirko
Fri, Oct 11, 2019 at 04:04:29AM CEST, jakub.kicin...@netronome.com wrote: >On Thu, 10 Oct 2019 15:18:49 +0200, Jiri Pirko wrote: >> From: Jiri Pirko >> >> During health reporter operations, driver might want to fill-up >> the extack message, so propagate extack down to the health reporter ops. >>

Re: [PATCH net] r8169: fix jumbo packet handling on resume from suspend

2019-10-10 Thread Heiner Kallweit
On 11.10.2019 01:36, Jakub Kicinski wrote: > On Wed, 9 Oct 2019 20:55:48 +0200, Heiner Kallweit wrote: >> Mariusz reported that invalid packets are sent after resume from >> suspend if jumbo packets are active. It turned out that his BIOS >> resets chip settings to non-jumbo on resume. Most chip se

Re: [PATCH V2 1/2] net: phy: micrel: Discern KSZ8051 and KSZ8795 PHYs

2019-10-10 Thread Simon Horman
On Thu, Oct 10, 2019 at 09:46:21PM +0200, Marek Vasut wrote: > The KSZ8051 PHY and the KSZ8794/KSZ8795/KSZ8765 switch share exactly the > same PHY ID. Since KSZ8051 is higher in the ksphy_driver[] list of PHYs > in the micrel PHY driver, it is used even with the KSZ87xx switch. This > is wrong, sin

Re: [PATCH net 1/4] net: aquantia: temperature retrieval fix

2019-10-10 Thread Simon Horman
On Thu, Oct 10, 2019 at 02:01:22PM +, Igor Russkikh wrote: > Chip temperature is a two byte word, colocated internally with cable > length data. We do all readouts from HW memory by dwords, thus > we should clear extra high bytes, otherwise temperature output > gets weird as soon as we attach a

Re: [PATCHv2 net-next 2/6] lwtunnel: add LWTUNNEL_IP_OPTS support for lwtunnel_ip

2019-10-10 Thread Simon Horman
On Thu, Oct 10, 2019 at 05:45:14PM +0800, Xin Long wrote: > On Wed, Oct 9, 2019 at 3:55 PM Simon Horman > wrote: > > > > On Tue, Oct 08, 2019 at 11:16:12PM +0800, Xin Long wrote: > > > This patch is to add LWTUNNEL_IP_OPTS into lwtunnel_ip_t, by which > > > users will be able to set options for i

Re: [Potential Spoof] [PATCH bpf-next] bpf: fix cast to pointer from integer of different size warning

2019-10-10 Thread Martin Lau
On Thu, Oct 10, 2019 at 09:29:25PM -0700, Andrii Nakryiko wrote: > Fix "warning: cast to pointer from integer of different size" when > casting u64 addr to void *. > > Reported-by: kbuild test robot > Signed-off-by: Andrii Nakryiko Fixes: a23740ec43ba ("bpf: Track contents of read-only maps as s

[PATCH bpf-next] bpf: fix cast to pointer from integer of different size warning

2019-10-10 Thread Andrii Nakryiko
Fix "warning: cast to pointer from integer of different size" when casting u64 addr to void *. Reported-by: kbuild test robot Signed-off-by: Andrii Nakryiko --- kernel/bpf/verifier.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.

Re: [PATCH net-next] Change in Openvswitch to support MPLS label depth of 3 in ingress direction

2019-10-10 Thread Martin Varghese
On Wed, Oct 09, 2019 at 08:29:51AM -0700, Pravin Shelar wrote: > On Mon, Oct 7, 2019 at 9:41 PM Martin Varghese > wrote: > > > > From: Martin Varghese > > > > The openvswitch was supporting a MPLS label depth of 1 in the ingress > > direction though the userspace OVS supports a max depth of 3 lab

[PATCH bpf-next] libbpf: handle invalid typedef emitted by old GCC

2019-10-10 Thread Andrii Nakryiko
Old GCC versions are producing invalid typedef for __gnuc_va_list pointing to void. Special-case this and emit valid: typedef __builtin_va_list __gnuc_va_list; Reported-by: John Fastabend Signed-off-by: Andrii Nakryiko --- tools/lib/bpf/btf_dump.c | 11 +++ 1 file changed, 11 insertion

[PATCH net-next] tcp: improve recv_skip_hint for tcp_zerocopy_receive

2019-10-10 Thread Soheil Hassas Yeganeh
From: Soheil Hassas Yeganeh tcp_zerocopy_receive() rounds down the zc->length a multiple of PAGE_SIZE. This results in two issues: - tcp_zerocopy_receive sets recv_skip_hint to the length of the receive queue if the zc->length input is smaller than the PAGE_SIZE, even though the data in recei

[PATCH net 4/9] tcp: annotate tp->write_seq lockless reads

2019-10-10 Thread Eric Dumazet
There are few places where we fetch tp->write_seq while this field can change from IRQ or other cpu. We need to add READ_ONCE() annotations, and also make sure write sides use corresponding WRITE_ONCE() to avoid store-tearing. Signed-off-by: Eric Dumazet --- include/net/tcp.h| 2 +- ne

[PATCH net 8/9] tcp: annotate sk->sk_sndbuf lockless reads

2019-10-10 Thread Eric Dumazet
For the sake of tcp_poll(), there are few places where we fetch sk->sk_sndbuf while this field can change from IRQ or other cpu. We need to add READ_ONCE() annotations, and also make sure write sides use corresponding WRITE_ONCE() to avoid store-tearing. Note that other transports probably need s

[PATCH net 3/9] tcp: annotate tp->copied_seq lockless reads

2019-10-10 Thread Eric Dumazet
There are few places where we fetch tp->copied_seq while this field can change from IRQ or other cpu. We need to add READ_ONCE() annotations, and also make sure write sides use corresponding WRITE_ONCE() to avoid store-tearing. Note that tcp_inq_hint() was already using READ_ONCE(tp->copied_seq)

[PATCH net 5/9] tcp: annotate tp->snd_nxt lockless reads

2019-10-10 Thread Eric Dumazet
There are few places where we fetch tp->snd_nxt while this field can change from IRQ or other cpu. We need to add READ_ONCE() annotations, and also make sure write sides use corresponding WRITE_ONCE() to avoid store-tearing. Signed-off-by: Eric Dumazet --- include/net/tcp.h| 3 ++- net

[PATCH net 6/9] tcp: annotate tp->urg_seq lockless reads

2019-10-10 Thread Eric Dumazet
There two places where we fetch tp->urg_seq while this field can change from IRQ or other cpu. We need to add READ_ONCE() annotations, and also make sure write side use corresponding WRITE_ONCE() to avoid store-tearing. Signed-off-by: Eric Dumazet --- net/ipv4/tcp.c | 5 +++-- net/ipv4/tc

[PATCH net 1/9] tcp: add rcu protection around tp->fastopen_rsk

2019-10-10 Thread Eric Dumazet
Both tcp_v4_err() and tcp_v6_err() do the following operations while they do not own the socket lock : fastopen = tp->fastopen_rsk; snd_una = fastopen ? tcp_rsk(fastopen)->snt_isn : tp->snd_una; The problem is that without appropriate barrier, the compiler might reload tp->fastope

[PATCH net 0/9] tcp: address KCSAN reports in tcp_poll() (part I)

2019-10-10 Thread Eric Dumazet
This all started with a KCSAN report (included in "tcp: annotate tp->rcv_nxt lockless reads" changelog) tcp_poll() runs in a lockless way. This means that about all accesses of tcp socket fields done in tcp_poll() context need annotations otherwise KCSAN will complain about data-races. While doin

[PATCH net 2/9] tcp: annotate tp->rcv_nxt lockless reads

2019-10-10 Thread Eric Dumazet
There are few places where we fetch tp->rcv_nxt while this field can change from IRQ or other cpu. We need to add READ_ONCE() annotations, and also make sure write sides use corresponding WRITE_ONCE() to avoid store-tearing. Note that tcp_inq_hint() was already using READ_ONCE(tp->rcv_nxt) syzbo

[PATCH net 7/9] tcp: annotate sk->sk_rcvbuf lockless reads

2019-10-10 Thread Eric Dumazet
For the sake of tcp_poll(), there are few places where we fetch sk->sk_rcvbuf while this field can change from IRQ or other cpu. We need to add READ_ONCE() annotations, and also make sure write sides use corresponding WRITE_ONCE() to avoid store-tearing. Note that other transports probably need s

[PATCH net 9/9] tcp: annotate sk->sk_wmem_queued lockless reads

2019-10-10 Thread Eric Dumazet
For the sake of tcp_poll(), there are few places where we fetch sk->sk_wmem_queued while this field can change from IRQ or other cpu. We need to add READ_ONCE() annotations, and also make sure write sides use corresponding WRITE_ONCE() to avoid store-tearing. sk_wmem_queued_add() helper is added

[PATCH bpf-next 0/2] selftests/bpf Makefile cleanup and fixes

2019-10-10 Thread Andrii Nakryiko
Patch #1 enforces libbpf build to have bpf_helper_defs.h ready before test BPF programs are built. Patch #2 drops obsolete BTF/pahole detection logic from Makefile. Andrii Nakryiko (2): selftests/bpf: enforce libbpf build before BPF programs are built selftests/bpf: remove obsolete pahole/BTF

[PATCH bpf-next 2/2] selftests/bpf: remove obsolete pahole/BTF support detection

2019-10-10 Thread Andrii Nakryiko
Given lots of selftests won't work without recent enough Clang/LLVM that fully supports BTF, there is no point in maintaining outdated BTF support detection and fall-back to pahole logic. Just assume we have everything we need. Signed-off-by: Andrii Nakryiko --- tools/testing/selftests/bpf/Makef

[PATCH bpf-next 1/2] selftests/bpf: enforce libbpf build before BPF programs are built

2019-10-10 Thread Andrii Nakryiko
Given BPF programs rely on libbpf's bpf_helper_defs.h, which is auto-generated during libbpf build, libbpf build has to happen before we attempt progs/*.c build. Enforce it as order-only dependency. Fixes: 24f25763d6de ("libbpf: auto-generate list of BPF helper definitions") Signed-off-by: Andrii

[PATCH bpf-next] libbpf: generate more efficient BPF_CORE_READ code

2019-10-10 Thread Andrii Nakryiko
Existing BPF_CORE_READ() macro generates slightly suboptimal code. If there are intermediate pointers to be read, initial source pointer is going to be assigned into a temporary variable and then temporary variable is going to be uniformly used as a "source" pointer for all intermediate pointer rea

Re: [PATCH v2 net 0/3] net/smc: fixes for -net

2019-10-10 Thread Jakub Kicinski
On Thu, 10 Oct 2019 10:16:08 +0200, Karsten Graul wrote: > Fixes for -net, addressing two races in SMC receive path and > add a missing cleanup when the link group creating fails with > ISM devices and a VLAN id. > > v1->v2: > - added fixes tags Applied, queued for stable

Re: [patch net-next v2 2/4] devlink: propagate extack down to health reporter ops

2019-10-10 Thread Jakub Kicinski
On Thu, 10 Oct 2019 15:18:49 +0200, Jiri Pirko wrote: > From: Jiri Pirko > > During health reporter operations, driver might want to fill-up > the extack message, so propagate extack down to the health reporter ops. > > Signed-off-by: Jiri Pirko > @@ -507,11 +507,14 @@ enum devlink_health_repo

Re: [PATCH net-next 1/2] ethtool: Add support for 400Gbps (50Gbps per lane) link modes

2019-10-10 Thread Jakub Kicinski
On Thu, 10 Oct 2019 09:32:02 +0300, Ido Schimmel wrote: > From: Jiri Pirko > > Signed-off-by: Jiri Pirko > Signed-off-by: Ido Schimmel I can't apply a patch without a commit message with a clear conscience, sorry :(

Re: [PATCH next] ipvlan: consolidate TSO flags using NETIF_F_ALL_TSO

2019-10-10 Thread Jakub Kicinski
On Wed, 9 Oct 2019 16:20:11 -0700, Mahesh Bandewar wrote: > This will ensure that any new TSO related flags added (which > would be part of ALL_TSO mask and IPvlan driver doesn't need > to update every time new flag gets added. > > Signed-off-by: Mahesh Bandewar > Suggested-by: Eric Dumazet Ap

RE: [net-next v3 2/7] net: reject PTP periodic output requests with unsupported flags

2019-10-10 Thread Brown, Aaron F
> From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] > On Behalf Of Jacob Keller > Sent: Thursday, September 26, 2019 11:11 AM > To: netdev@vger.kernel.org > Cc: Intel Wired LAN ; Kirsher, Jeffrey T > ; Keller, Jacob E ; > Richard Cochran ; Felipe Balbi > ; David S . Miller ;

RE: [net-next v3 1/7] ptp: correctly disable flags on old ioctls

2019-10-10 Thread Brown, Aaron F
> From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org] > On Behalf Of Jacob Keller > Sent: Thursday, September 26, 2019 11:11 AM > To: netdev@vger.kernel.org > Cc: Intel Wired LAN ; Kirsher, Jeffrey T > ; Keller, Jacob E ; > Richard Cochran ; Felipe Balbi > ; David S . Miller ;

RE: [Intel-wired-lan] [net-next v3 5/7] igb: reject unsupported external timestamp flags

2019-10-10 Thread Brown, Aaron F
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On Behalf Of > Jacob Keller > Sent: Thursday, September 26, 2019 11:11 AM > To: netdev@vger.kernel.org > Cc: Intel Wired LAN > Subject: [Intel-wired-lan] [net-next v3 5/7] igb: reject unsupported external > timestamp flags > > Fi

Re: [PATCHv2 next] blackhole_netdev: fix syzkaller reported issue

2019-10-10 Thread Wei Wang
On Thu, Oct 10, 2019 at 9:48 AM Mahesh Bandewar wrote: > > While invalidating the dst, we assign backhole_netdev instead of > loopback device. However, this device does not have idev pointer > and hence no ip6_ptr even if IPv6 is enabled. Possibly this has > triggered the syzbot reported crash. >

RE: [PATCH 0/3] igb, ixgbe, i40e UDP segmentation offload support

2019-10-10 Thread Brown, Aaron F
> -Original Message- > From: Josh Hunt [mailto:joh...@akamai.com] > Sent: Thursday, October 10, 2019 5:28 PM > To: Brown, Aaron F ; Alexander Duyck > ; Bowers, AndrewX > > Cc: Netdev ; Willem de Bruijn > ; intel-wired-lan > Subject: Re: [PATCH 0/3] igb, ixgbe, i40e UDP segmentation offl

[PATCH v5 bpf-next 14/15] samples/bpf: add sysroot support

2019-10-10 Thread Ivan Khoronzhuk
Basically it only enables that was added by previous couple fixes. Sysroot contains correct libs installed and its headers. Useful when working with NFC or virtual machine. Usage example: clean (on demand) make ARCH=arm -C samples/bpf clean make ARCH=arm -C tools clean make ARCH=arm c

[PATCH v5 bpf-next 05/15] samples/bpf: use __LINUX_ARM_ARCH__ selector for arm

2019-10-10 Thread Ivan Khoronzhuk
For arm, -D__LINUX_ARM_ARCH__=X is min version used as instruction set selector and is absolutely required while parsing some parts of headers. It's present in KBUILD_CFLAGS but not in autoconf.h, so let's retrieve it from and add to programs cflags. In another case errors like "SMP is not supporte

[PATCH v5 bpf-next 10/15] samples/bpf: use target CC environment for HDR_PROBE

2019-10-10 Thread Ivan Khoronzhuk
No need in hacking HOSTCC to be cross-compiler any more, so drop this trick and use target CC for HDR_PROBE. Acked-by: Andrii Nakryiko Signed-off-by: Ivan Khoronzhuk --- samples/bpf/Makefile | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/samples/bpf/Makefile b/samples/

[PATCH v5 bpf-next 06/15] samples/bpf: drop unnecessarily inclusion for bpf_load

2019-10-10 Thread Ivan Khoronzhuk
Drop inclusion for bpf_load -I$(objtree)/usr/include as it is included for all objects anyway, with above line: KBUILD_HOSTCFLAGS += -I$(objtree)/usr/include Acked-by: Andrii Nakryiko Signed-off-by: Ivan Khoronzhuk --- samples/bpf/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH v5 bpf-next 08/15] samples/bpf: base target programs rules on Makefile.target

2019-10-10 Thread Ivan Khoronzhuk
The main reason for that - HOSTCC and CC have different aims. HOSTCC is used to build programs running on host, that can cross-comple target programs with CC. It was tested for arm and arm64 cross compilation, based on linaro toolchain, but should work for others. So, in order to split cross compi

[PATCH v5 bpf-next 13/15] samples/bpf: provide C/LDFLAGS to libbpf

2019-10-10 Thread Ivan Khoronzhuk
In order to build lib using C/LD flags of target arch, provide them to libbpf make. Signed-off-by: Ivan Khoronzhuk --- samples/bpf/Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/samples/bpf/Makefile b/samples/bpf/Makefile index a6c33496e8ca..6b161326ac67 100644 --

Re: [PATCH 0/3] igb, ixgbe, i40e UDP segmentation offload support

2019-10-10 Thread Josh Hunt
On 10/10/19 5:21 PM, Brown, Aaron F wrote: Adding Andrew as he is most likely going to be testing this patch. Unfortunately my mail server flags attached scripts as potential threats and strips them out. Can you resent it as an tar file? I don't believe it's smart enough to open up tar and f

[PATCH v2 3/3] i40e: Add UDP segmentation offload support

2019-10-10 Thread Josh Hunt
Based on a series from Alexander Duyck this change adds UDP segmentation offload support to the i40e driver. CC: Alexander Duyck CC: Willem de Bruijn Signed-off-by: Josh Hunt --- drivers/net/ethernet/intel/i40e/i40e_main.c | 1 + drivers/net/ethernet/intel/i40e/i40e_txrx.c | 12 +---

[PATCH v2 1/3] igb: Add UDP segmentation offload support

2019-10-10 Thread Josh Hunt
Based on a series from Alexander Duyck this change adds UDP segmentation offload support to the igb driver. CC: Alexander Duyck CC: Willem de Bruijn Signed-off-by: Josh Hunt --- drivers/net/ethernet/intel/igb/e1000_82575.h | 1 + drivers/net/ethernet/intel/igb/igb_main.c| 23 +

[PATCH v2 2/3] ixgbe: Add UDP segmentation offload support

2019-10-10 Thread Josh Hunt
Repost from a series by Alexander Duyck to add UDP segmentation offload support to the igb driver: https://lore.kernel.org/netdev/20180504003916.4769.66271.stgit@localhost.localdomain/ CC: Alexander Duyck CC: Willem de Bruijn Suggested-by: Alexander Duyck Signed-off-by: Josh Hunt --- drivers/

[PATCH v2 0/3] igb, ixgbe, i40e UDP segmentation offload support

2019-10-10 Thread Josh Hunt
Alexander Duyck posted a series in 2018 proposing adding UDP segmentation offload support to ixgbe and ixgbevf, but those patches were never accepted: https://lore.kernel.org/netdev/20180504003556.4769.11407.stgit@localhost.localdomain/ This series is a repost of his ixgbe patch along with a simi

RE: [PATCH 0/3] igb, ixgbe, i40e UDP segmentation offload support

2019-10-10 Thread Brown, Aaron F
Adding Andrew as he is most likely going to be testing this patch. Unfortunately my mail server flags attached scripts as potential threats and strips them out. Can you resent it as an tar file? I don't believe it's smart enough to open up tar and flag it as a script. > -Original Message-

Re: [PATCH 0/3] igb, ixgbe, i40e UDP segmentation offload support

2019-10-10 Thread Josh Hunt
On 10/10/19 2:32 PM, Alexander Duyck wrote: On Thu, Oct 10, 2019 at 2:17 PM Josh Hunt wrote: On 10/9/19 3:44 PM, Alexander Duyck wrote: On Wed, Oct 9, 2019 at 3:08 PM Josh Hunt wrote: Alexander Duyck posted a series in 2018 proposing adding UDP segmentation offload support to ixgbe and ixg

Re: [PATCH v4 bpf-next 1/3] uapi/bpf: fix helper docs

2019-10-10 Thread Daniel Borkmann
On Tue, Oct 08, 2019 at 04:32:01PM -0700, Andrii Nakryiko wrote: > On Tue, Oct 8, 2019 at 2:49 PM Daniel Borkmann wrote: > > On Mon, Oct 07, 2019 at 10:47:19AM -0700, Andrii Nakryiko wrote: > > > On Mon, Oct 7, 2019 at 2:43 AM Daniel Borkmann > > > wrote: > > > > On Sun, Oct 06, 2019 at 08:07:36

Re: [PATCH net-next 1/1] tc-testing: updated pedit test cases

2019-10-10 Thread Jakub Kicinski
On Wed, 9 Oct 2019 16:53:51 -0400, Roman Mashak wrote: > Added test case for layered IP operation for a single source IP4/IP6 > address and a single destination IP4/IP6 address. > > Signed-off-by: Roman Mashak Applied, thanks

Re: [PATCH v2 bpf-next 0/2] Track read-only map contents as known scalars in BPF verifiers

2019-10-10 Thread Daniel Borkmann
On Wed, Oct 09, 2019 at 01:14:56PM -0700, Andrii Nakryiko wrote: > With BPF maps supporting direct map access (currently, array_map w/ single > element, used for global data) that are read-only both from system call and > BPF side, it's possible for BPF verifier to track its contents as known > con

Re: [net v2] net: update net_dim documentation after rename

2019-10-10 Thread Jakub Kicinski
On Wed, 9 Oct 2019 12:18:31 -0700, Jacob Keller wrote: > Commit 8960b38932be ("linux/dim: Rename externally used net_dim > members") renamed the net_dim API, removing the "net_" prefix from the > structures and functions. The patch didn't update the net_dim.txt > documentation file. > > Fix the d

Re: [PATCH bpf-next v2 0/2] Atomic flow dissector updates

2019-10-10 Thread Daniel Borkmann
On Thu, Oct 10, 2019 at 08:17:48PM +0200, Jakub Sitnicki wrote: > This patch set changes how bpf(BPF_PROG_ATTACH) operates on flow dissector > hook when there is already a program attached. After this change the user > is allowed to update the program in a single syscall. Please see the first > pat

RE: [PATCH net-next v1] documentation: correct include file reference

2019-10-10 Thread Keller, Jacob E
> -Original Message- > From: netdev-ow...@vger.kernel.org On > Behalf Of Jesse Brandeburg > Sent: Thursday, October 10, 2019 12:31 PM > To: netdev@vger.kernel.org > Subject: [PATCH net-next v1] documentation: correct include file reference > > The documentation had a reference to a filena

Re: [PATCH net] r8169: fix jumbo packet handling on resume from suspend

2019-10-10 Thread Jakub Kicinski
On Wed, 9 Oct 2019 20:55:48 +0200, Heiner Kallweit wrote: > Mariusz reported that invalid packets are sent after resume from > suspend if jumbo packets are active. It turned out that his BIOS > resets chip settings to non-jumbo on resume. Most chip settings are > re-initialized on resume from suspe

[PATCH] Documentation: networking: add a chapter for the DIM library

2019-10-10 Thread Randy Dunlap
umentation/networking/lib-dim.rst |6 ++ 2 files changed, 7 insertions(+) --- linux-next-20191010.orig/Documentation/networking/index.rst +++ linux-next-20191010/Documentation/networking/index.rst @@ -33,6 +33,7 @@ Contents: scaling tls tls-offload + lib-dim .. only:: subprojec

Re: [PATCH 0/3] igb, ixgbe, i40e UDP segmentation offload support

2019-10-10 Thread Alexander Duyck
On Thu, Oct 10, 2019 at 2:17 PM Josh Hunt wrote: > > On 10/9/19 3:44 PM, Alexander Duyck wrote: > > On Wed, Oct 9, 2019 at 3:08 PM Josh Hunt wrote: > >> > >> Alexander Duyck posted a series in 2018 proposing adding UDP segmentation > >> offload support to ixgbe and ixgbevf, but those patches were

Re: [PATCH 0/3] igb, ixgbe, i40e UDP segmentation offload support

2019-10-10 Thread Josh Hunt
On 10/9/19 3:44 PM, Alexander Duyck wrote: On Wed, Oct 9, 2019 at 3:08 PM Josh Hunt wrote: Alexander Duyck posted a series in 2018 proposing adding UDP segmentation offload support to ixgbe and ixgbevf, but those patches were never accepted: https://lore.kernel.org/netdev/20180504003556.4769.

Re: [PATCH 24/29] can: ti_hecc: add fifo underflow error reporting

2019-10-10 Thread Marc Kleine-Budde
On 10/10/19 7:51 PM, Jeroen Hofstee wrote: >>> When the rx fifo overflows the ti_hecc would silently drop them since >>> the overwrite protection is enabled for all mailboxes. So disable it >>> for the lowest priority mailbox and increment the rx_fifo_errors when >>> receive message lost is set. Dr

Re: [PATCH bpf-next v2 0/2] Atomic flow dissector updates

2019-10-10 Thread Stanislav Fomichev
On 10/10, Jakub Sitnicki wrote: > This patch set changes how bpf(BPF_PROG_ATTACH) operates on flow dissector > hook when there is already a program attached. After this change the user > is allowed to update the program in a single syscall. Please see the first > patch for rationale. > > v1 -> v2:

[PATCH V2 1/2] net: phy: micrel: Discern KSZ8051 and KSZ8795 PHYs

2019-10-10 Thread Marek Vasut
The KSZ8051 PHY and the KSZ8794/KSZ8795/KSZ8765 switch share exactly the same PHY ID. Since KSZ8051 is higher in the ksphy_driver[] list of PHYs in the micrel PHY driver, it is used even with the KSZ87xx switch. This is wrong, since the KSZ8051 configures registers of the PHY which are not present

[PATCH V2 2/2] net: phy: micrel: Update KSZ87xx PHY name

2019-10-10 Thread Marek Vasut
The KSZ8795 PHY ID is in fact used by KSZ8794/KSZ8795/KSZ8765 switches. Update the PHY ID and name to reflect that, as this family of switches is commonly refered to as KSZ87xx Signed-off-by: Marek Vasut Cc: Andrew Lunn Cc: David S. Miller Cc: Florian Fainelli Cc: George McCollister Cc: Heine

Re: [PATCH bpf-next v2 2/2] selftests/bpf: Check that flow dissector can be re-attached

2019-10-10 Thread Martin Lau
On Thu, Oct 10, 2019 at 08:17:50PM +0200, Jakub Sitnicki wrote: > Make sure a new flow dissector program can be attached to replace the old > one with a single syscall. Also check that attaching the same program twice > is prohibited. > > Signed-off-by: Jakub Sitnicki Acked-by: Martin KaFai Lau

Re: [PATCH bpf-next v2 1/2] flow_dissector: Allow updating the flow dissector program atomically

2019-10-10 Thread Martin Lau
On Thu, Oct 10, 2019 at 08:17:49PM +0200, Jakub Sitnicki wrote: > It is currently not possible to detach the flow dissector program and > attach a new one in an atomic fashion, that is with a single syscall. > Attempts to do so will be met with EEXIST error. > > This makes updates to flow dissecto

[PATCH net-next v1] documentation: correct include file reference

2019-10-10 Thread Jesse Brandeburg
The documentation had a reference to a filename before a rename had been completed. Fix the name so the documentation is correct. Signed-off-by: Jesse Brandeburg --- Documentation/networking/net_dim.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/networking

Re: [PATCH 1/2] net: phy: micrel: Discern KSZ8051 and KSZ8795 PHYs

2019-10-10 Thread Heiner Kallweit
On 10.10.2019 21:12, Marek Vasut wrote: > The KSZ8051 PHY and the KSZ8794/KSZ8795/KSZ8765 switch share exactly the > same PHY ID. Since KSZ8051 is higher in the ksphy_driver[] list of PHYs > in the micrel PHY driver, it is used even with the KSZ87xx switch. This > is wrong, since the KSZ8051 config

[PATCH 1/2] net: phy: micrel: Discern KSZ8051 and KSZ8795 PHYs

2019-10-10 Thread Marek Vasut
The KSZ8051 PHY and the KSZ8794/KSZ8795/KSZ8765 switch share exactly the same PHY ID. Since KSZ8051 is higher in the ksphy_driver[] list of PHYs in the micrel PHY driver, it is used even with the KSZ87xx switch. This is wrong, since the KSZ8051 configures registers of the PHY which are not present

[PATCH 2/2] net: phy: micrel: Update KSZ87xx PHY name

2019-10-10 Thread Marek Vasut
The KSZ8795 PHY ID is in fact used by KSZ8794/KSZ8795/KSZ8765 switches. Update the PHY ID and name to reflect that, as this family of switches is commonly refered to as KSZ87xx Signed-off-by: Marek Vasut Cc: Andrew Lunn Cc: David S. Miller Cc: Florian Fainelli Cc: George McCollister Cc: Heine

Re: [PATCH v2 bpf-next 12/12] selftests/bpf: add kfree_skb raw_tp test

2019-10-10 Thread Alexei Starovoitov
On Thu, Oct 10, 2019 at 02:07:29PM +0300, Ido Schimmel wrote: > On Wed, Oct 09, 2019 at 09:15:03PM -0700, Alexei Starovoitov wrote: > > +SEC("raw_tracepoint/kfree_skb") > > +int trace_kfree_skb(struct trace_kfree_skb *ctx) > > +{ > > + struct sk_buff *skb = ctx->skb; > > + struct net_device *de

[RFC PATCH net] netns: fix GFP flags in rtnl_net_notifyid()

2019-10-10 Thread Guillaume Nault
In rtnl_net_notifyid(), we certainly can't pass a null GFP flag to rtnl_notify(). A GFP_KERNEL flag would be fine in most circumstances, but there are a few paths calling rtnl_net_notifyid() from atomic context or from RCU critical section. The later also precludes the use of gfp_any() as it wouldn

[PATCH net 2/2] net/sched: fix corrupted L2 header with MPLS 'push' and 'pop' actions

2019-10-10 Thread Davide Caratti
the following script: # tc qdisc add dev eth0 clsact # tc filter add dev eth0 egress protocol ip matchall \ > action mpls push protocol mpls_uc label 0x355aa bos 1 causes corruption of all IP packets transmitted by eth0. On TC egress, we can't rely on the value of skb->mac_len, because it's 0

[PATCH net 1/2] net: avoid errors when trying to pop MLPS header on non-MPLS packets

2019-10-10 Thread Davide Caratti
the following script: # tc qdisc add dev eth0 clsact # tc filter add dev eth0 egress matchall action mpls pop implicitly makes the kernel drop all packets transmitted by eth0, if they don't have a MPLS header. This behavior is uncommon: other encapsulations (like VLAN) just let the packet pass

[PATCH net 0/2] net/sched: fix wrong behavior of MPLS push/pop action

2019-10-10 Thread Davide Caratti
this series contains two fixes for TC 'act_mpls', that try to address two problems that can be observed configuring simple 'push' / 'pop' operations: - patch 1/2 avoids dropping non-MPLS packets that pass through the MPLS 'pop' action. - patch 2/2 fixes corruption of the L2 header that occurs whe

Re: [PATCH 2/2] netfilter: revert "conntrack: silent a memory leak warning"

2019-10-10 Thread Cong Wang
On Tue, Oct 8, 2019 at 12:10 AM Maciej Żenczykowski wrote: > > Here's my reasoning: > > old = ct->ext; > > //... stuff that doesn't change old. > > alloc = max(newlen, NF_CT_EXT_PREALLOC); <-- will be >= 128, > so not zero > kmemleak_not_leak(old); > new =

[PATCH 2/2] net: dsa: microchip: Add shared regmap mutex

2019-10-10 Thread Marek Vasut
The KSZ driver uses one regmap per register width (8/16/32), each with it's own lock, but accessing the same set of registers. In theory, it is possible to create a race condition between these regmaps, although the underlying bus (SPI or I2C) locking should assure nothing bad will really happen an

[PATCH 1/2] net: dsa: microchip: Do not reinit mutexes on KSZ87xx

2019-10-10 Thread Marek Vasut
The KSZ87xx driver calls mutex_init() on mutexes already inited in ksz_common.c ksz_switch_register(). Do not do it twice, drop the reinitialization. Signed-off-by: Marek Vasut Cc: Andrew Lunn Cc: David S. Miller Cc: Florian Fainelli Cc: George McCollister Cc: Tristram Ha Cc: Woojung Huh --

Re: [PATCH net-next v7 09/17] ethtool: generic handlers for GET requests

2019-10-10 Thread Johannes Berg
On Thu, 2019-10-10 at 20:04 +0200, Michal Kubecek wrote: > > The only thing I don't like about the genetlink infrastructure is the > design decision that policy and corresponding maxattr is an attribute of > the family rather than a command. This forces anyone who wants to use it > to essentially

[PATCH bpf-next v2 2/2] selftests/bpf: Check that flow dissector can be re-attached

2019-10-10 Thread Jakub Sitnicki
Make sure a new flow dissector program can be attached to replace the old one with a single syscall. Also check that attaching the same program twice is prohibited. Signed-off-by: Jakub Sitnicki --- .../bpf/prog_tests/flow_dissector_reattach.c | 127 ++ 1 file changed, 127 inser

Re: [PATCH net-next v7 13/17] ethtool: add standard notification handler

2019-10-10 Thread Michal Kubecek
On Thu, Oct 10, 2019 at 05:25:59PM +0200, Jiri Pirko wrote: > Wed, Oct 09, 2019 at 10:59:40PM CEST, mkube...@suse.cz wrote: > >+static void *ethnl_bcastmsg_put(struct sk_buff *skb, u8 cmd) > >+{ > >+return genlmsg_put(skb, 0, ++ethnl_bcast_seq, ðtool_genl_family, 0, > >+ c

[PATCH bpf-next v2 0/2] Atomic flow dissector updates

2019-10-10 Thread Jakub Sitnicki
This patch set changes how bpf(BPF_PROG_ATTACH) operates on flow dissector hook when there is already a program attached. After this change the user is allowed to update the program in a single syscall. Please see the first patch for rationale. v1 -> v2: - Don't use CHECK macro which expects BPF

[PATCH bpf-next v2 1/2] flow_dissector: Allow updating the flow dissector program atomically

2019-10-10 Thread Jakub Sitnicki
It is currently not possible to detach the flow dissector program and attach a new one in an atomic fashion, that is with a single syscall. Attempts to do so will be met with EEXIST error. This makes updates to flow dissector program hard. Traffic steering that relies on BPF-powered flow dissectio

Re: [PATCH net-next v7 10/17] ethtool: provide string sets with STRSET_GET request

2019-10-10 Thread Michal Kubecek
On Thu, Oct 10, 2019 at 03:59:17PM +0200, Jiri Pirko wrote: > Wed, Oct 09, 2019 at 10:59:30PM CEST, mkube...@suse.cz wrote: > > [...] > > >+const struct get_request_ops strset_request_ops = { > > I think when var is leaving context of single file, it should have > prefix: > ethnl_strset_request_

Re: [PATCH 24/29] can: ti_hecc: add fifo underflow error reporting

2019-10-10 Thread Jeroen Hofstee
Attempt 2, now as plain text... (vger doesn't like html) On 10/10/19 5:52 PM, Marc Kleine-Budde wrote: > On 10/10/19 2:17 PM, Marc Kleine-Budde wrote: >> From: Jeroen Hofstee >> >> When the rx fifo overflows the ti_hecc would silently drop them since >> the overwrite protection is enabled for all

Re: [PATH bpf-next 2/2] selftests/bpf: Check that flow dissector can be re-attached

2019-10-10 Thread Stanislav Fomichev
On 10/10, Jakub Sitnicki wrote: > On Thu, Oct 10, 2019 at 06:31 PM CEST, Stanislav Fomichev wrote: > > On 10/10, Jakub Sitnicki wrote: > >> On Wed, Oct 09, 2019 at 06:33 PM CEST, Stanislav Fomichev wrote: > >> > On 10/09, Jakub Sitnicki wrote: > > [...] > > >> >> +/* Not used here. For CHECK macr

Re: [PATH bpf-next 2/2] selftests/bpf: Check that flow dissector can be re-attached

2019-10-10 Thread Jakub Sitnicki
On Thu, Oct 10, 2019 at 06:31 PM CEST, Stanislav Fomichev wrote: > On 10/10, Jakub Sitnicki wrote: >> On Wed, Oct 09, 2019 at 06:33 PM CEST, Stanislav Fomichev wrote: >> > On 10/09, Jakub Sitnicki wrote: [...] >> >> +/* Not used here. For CHECK macro sake only. */ >> >> +static int duration; >> >

[PATCHv2 next] blackhole_netdev: fix syzkaller reported issue

2019-10-10 Thread Mahesh Bandewar
While invalidating the dst, we assign backhole_netdev instead of loopback device. However, this device does not have idev pointer and hence no ip6_ptr even if IPv6 is enabled. Possibly this has triggered the syzbot reported crash. The syzbot report does not have reproducer, however, this is the on

Re: [PATH bpf-next 2/2] selftests/bpf: Check that flow dissector can be re-attached

2019-10-10 Thread Stanislav Fomichev
On 10/10, Jakub Sitnicki wrote: > On Wed, Oct 09, 2019 at 06:33 PM CEST, Stanislav Fomichev wrote: > > On 10/09, Jakub Sitnicki wrote: > >> Make sure a new flow dissector program can be attached to replace the old > >> one with a single syscall. Also check that attaching the same program twice > >>

[PATCH net 0/2] dpaa2-eth: misc fixes

2019-10-10 Thread Ioana Ciornei
This patch set adds a couple of fixes around updating configuration on MAC change. Depending on when MC connects the DPNI to a MAC, both the MAC address and TX FQIDs should be updated everytime there is a change in configuration. Florin Chiculita (1): dpaa2-eth: add irq for the dpmac connect/di

[PATCH net 2/2] dpaa2-eth: Fix TX FQID values

2019-10-10 Thread Ioana Ciornei
From: Ioana Radulescu Depending on when MC connects the DPNI to a MAC, Tx FQIDs may not be available during probe time. Read the FQIDs each time the link goes up to avoid using invalid values. In case an error occurs or an invalid value is retrieved, fall back to QDID-based enqueueing. Fixes: 1

[PATCH net 1/2] dpaa2-eth: add irq for the dpmac connect/disconnect event

2019-10-10 Thread Ioana Ciornei
From: Florin Chiculita Add IRQ for the DPNI endpoint change event, resolving the issue when a dynamically created DPNI gets a randomly generated hw address when the endpoint is a DPMAC object. Signed-off-by: Florin Chiculita Signed-off-by: Ioana Ciornei --- drivers/net/ethernet/freescale/dpaa

Re: [patch net-next 2/4] devlink: propagate extack down to health reporter ops

2019-10-10 Thread Jakub Kicinski
On Thu, 10 Oct 2019 10:07:04 +0200, Jiri Pirko wrote: > Thu, Oct 10, 2019 at 05:38:18AM CEST, jakub.kicin...@netronome.com wrote: > >On Wed, 9 Oct 2019 13:04:43 +0200, Jiri Pirko wrote: > >> From: Jiri Pirko > >> > >> During health reporter operations, driver might want to fill-up > >> the ext

Re: [PATCH 24/29] can: ti_hecc: add fifo underflow error reporting

2019-10-10 Thread Marc Kleine-Budde
On 10/10/19 2:17 PM, Marc Kleine-Budde wrote: > From: Jeroen Hofstee > > When the rx fifo overflows the ti_hecc would silently drop them since > the overwrite protection is enabled for all mailboxes. So disable it > for the lowest priority mailbox and increment the rx_fifo_errors when > receive m

[PATCH net-next] ipv4: Return -ENETUNREACH if we can't create route but saddr is valid

2019-10-10 Thread Stefano Brivio
...instead of -EINVAL. An issue was found with older kernel versions while unplugging a NFS client with pending RPCs, and the wrong error code here prevented it from recovering once link is back up with a configured address. Incidentally, this is not an issue anymore since commit 4f8943f80883 ("SU

[PATCH net 4/4] net: aquantia: correctly handle macvlan and multicast coexistence

2019-10-10 Thread Igor Russkikh
From: Dmitry Bogdanov macvlan and multicast handling is now mixed up. The explicit issue is that macvlan interface gets broken (no traffic) after clearing MULTICAST flag on the real interface. We now do separate logic and consider both ALLMULTI and MULTICAST flags on the device. Fixes: 11ba961c

[PATCH net 2/4] net: aquantia: when cleaning hw cache it should be toggled

2019-10-10 Thread Igor Russkikh
>From HW specification to correctly reset HW caches (this is a required workaround when stopping the device), register bit should actually be toggled. It was previosly always just set. Due to the way driver stops HW this never actually caused any issues, but it still may, so cleaning this up. Fix

[PATCH net 0/4] Aquantia/Marvell AQtion atlantic driver fixes 10/2019

2019-10-10 Thread Igor Russkikh
Hello David! Here is a set of various bugfixes, to be considered for stable as well. Thanks! Dmitry Bogdanov (2): net: aquantia: do not pass lro session with invalid tcp checksum net: aquantia: correctly handle macvlan and multicast coexistence Igor Russkikh (2): net: aquantia: temperatur

[PATCH net 1/4] net: aquantia: temperature retrieval fix

2019-10-10 Thread Igor Russkikh
Chip temperature is a two byte word, colocated internally with cable length data. We do all readouts from HW memory by dwords, thus we should clear extra high bytes, otherwise temperature output gets weird as soon as we attach a cable to the NIC. Fixes: 8f8940118654 ("net: aquantia: add infrastruc

[PATCH net 3/4] net: aquantia: do not pass lro session with invalid tcp checksum

2019-10-10 Thread Igor Russkikh
From: Dmitry Bogdanov Individual descriptors on LRO TCP session should be checked for CRC errors. It was discovered that HW recalculates L4 checksums on LRO session and does not break it up on bad L4 csum. Thus, driver should aggregate HW LRO L4 statuses from all individual buffers of LRO sessio

Apply For Financial investment at a lower rate 2%

2019-10-10 Thread Valentina Yurina
-- Hello, We are private lenders based in UK. Do you need a loan (credit) as soon as possible. Are you in search of money to solve your personal needs or finance your business venture, then get Your desired loan today! Consult us at Sunrise Funding Ltd. * We offer personal loan & huge capital l

[patch net-next v2 1/4] devlink: don't do reporter recovery if the state is healthy

2019-10-10 Thread Jiri Pirko
From: Jiri Pirko If reporter state is healthy, don't call into a driver for recover and don't increase recovery count. Signed-off-by: Jiri Pirko --- net/core/devlink.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/net/core/devlink.c b/net/core/devlink.c index eb0a22f05887..95887462eec

[patch net-next v2 4/4] selftests: add netdevsim devlink health tests

2019-10-10 Thread Jiri Pirko
From: Jiri Pirko Add basic tests to verify functionality of netdevsim reporters. Signed-off-by: Jiri Pirko --- v1->v2: - added test of manual recovery fail Signed-off-by: Jiri Pirko --- .../drivers/net/netdevsim/devlink.sh | 127 +- 1 file changed, 126 insertions(+),

  1   2   >