Re: [PATCH net-next 1/3] devlink: Add fw_version_check generic parameter

2018-11-07 Thread Jakub Kicinski
On Wed, 7 Nov 2018 12:11:32 +0200, Ido Schimmel wrote: > On Tue, Nov 06, 2018 at 02:47:13PM -0800, Jakub Kicinski wrote: > > On Tue, 6 Nov 2018 22:37:51 +0200, Ido Schimmel wrote: > > > On Tue, Nov 06, 2018 at 12:19:13PM -0800, Jakub Kicinski wrote: > > > > We have a FW loading policy for NFP,

Re: [PATCH v4 1/3] net: emac: implement 802.1Q VLAN TX tagging support

2018-11-07 Thread David Miller
From: David Miller Date: Tue, 06 Nov 2018 15:09:54 -0800 (PST) > From: Christian Lamparter > Date: Tue, 6 Nov 2018 23:27:49 +0100 > >> @@ -1435,6 +1436,22 @@ static inline netdev_tx_t emac_xmit_finish(struct >> emac_instance *dev, int len) >> return NETDEV_TX_OK; >> } >> >> +static

[PATCH net-next 3/5] net: phy: add phy_check_link_status

2018-11-07 Thread Heiner Kallweit
In few places in the state machine the state is set to PHY_RUNNING or PHY_NOLINK after doing a phy_read_status(). So factor this out to phy_check_link_status(). First use it in phy_start_aneg(): By setting the state to PHY_RUNNING or PHY_NOLINK directly we can remove the code to handle the case

[PATCH net-next 5/5] net: phy: use phy_check_link_status in more places in the state machine

2018-11-07 Thread Heiner Kallweit
Use phy_check_link_status in more places in the state machine. Signed-off-by: Heiner Kallweit --- drivers/net/phy/phy.c | 53 --- 1 file changed, 5 insertions(+), 48 deletions(-) diff --git a/drivers/net/phy/phy.c b/drivers/net/phy/phy.c index

[PATCH net-next 4/5] net: phy: remove state PHY_AN

2018-11-07 Thread Heiner Kallweit
After the recent changes in the state machine state PHY_AN isn't used any longer and can be removed. Signed-off-by: Heiner Kallweit --- drivers/net/phy/phy.c | 27 --- include/linux/phy.h | 19 +-- 2 files changed, 1 insertion(+), 45 deletions(-) diff

Re: [PATCH net-next 0/5] net: phy: improve and simplify phylib state machine

2018-11-07 Thread Andrew Lunn
On Wed, Nov 07, 2018 at 08:41:52PM +0100, Heiner Kallweit wrote: > This patch series is based on two axioms: > > - During autoneg a PHY always reports the link being down Hi Heiner I think that is a risky assumption to make. What happens if this assumption is incorrect? Andrew

[PATCH net-next 2/5] net: phy: remove useless check in state machine case PHY_RESUMING

2018-11-07 Thread Heiner Kallweit
If aneg isn't finished yet then the PHY reports the link as down. There's no benefit in setting the state to PHY_AN because the next state machine run would set the status to PHY_NOLINK anyway (except in the meantime aneg has been finished and link is up). Therefore we can set the state to

Re: [PATCH iproute2 net-next 1/2] iplink_vxlan: Add DF configuration

2018-11-07 Thread David Ahern
On 11/6/18 2:39 PM, Stefano Brivio wrote: > diff --git a/ip/iplink_vxlan.c b/ip/iplink_vxlan.c > index 7fc0e2b4eb06..86afbe1334f0 100644 > --- a/ip/iplink_vxlan.c > +++ b/ip/iplink_vxlan.c > @@ -31,6 +31,7 @@ static void print_explain(FILE *f) > " [ local ADDR ]\n" >

Re: [PATCH bpf-next 2/2] bpftool: support loading flow dissector

2018-11-07 Thread Jakub Kicinski
On Wed, 7 Nov 2018 11:35:52 -0800, Stanislav Fomichev wrote: > This commit adds support for loading/attaching/detaching flow > dissector program. The structure of the flow dissector program is > assumed to be the same as in the selftests: > > * flow_dissector section with the main entry point >

Re: [PATCH net-next 00/10] udp: implement GRO support

2018-11-07 Thread David Miller
From: Willem de Bruijn Date: Wed, 7 Nov 2018 13:56:52 -0600 > For the series: > > Acked-by: Willem de Bruijn > > (Let me know if I need to Ack each patch directly) You do not. This is why I like header postings so much, reviewers can just reply to it to ACK the entire series.

Re: [PATCH bpf-next v2 02/13] bpf: btf: Add BTF_KIND_FUNC and BTF_KIND_FUNC_PROTO

2018-11-07 Thread Edward Cree
On 07/11/18 00:59, Alexei Starovoitov wrote: > Function name and function argument names are part of the same debug info. > Splitting them makes no sense. ... except where combining them involves creating pain elsewhere. Sure the function name *could* go in the type record, but there  still needs

Re: [PATCH net-next 07/11] selftests: pmtu: Introduce tests for IPv4/IPv6 over GENEVE over IPv6

2018-11-07 Thread David Ahern
On 11/6/18 2:39 PM, Stefano Brivio wrote: > This only introduces tests over GENEVE over IPv6 right now. I'll introduce > tests over IPv4 (they can be added trivially) once DF configuration support > is accepted into iproute2. same here.

Re: [PATCH net-next 00/10] udp: implement GRO support

2018-11-07 Thread Willem de Bruijn
On Wed, Nov 7, 2018 at 5:43 AM Paolo Abeni wrote: > > This series implements GRO support for UDP sockets, as the RX counterpart > of commit bec1f6f69736 ("udp: generate gso with UDP_SEGMENT"). > The core functionality is implemented by the second patch, introducing a new > sockopt to enable

[PATCH net-next 1/2] net: phy: use phy_id_mask value zero for exact match

2018-11-07 Thread Heiner Kallweit
A phy_id_mask value zero means every PHYID matches, therefore value zero isn't used. So we can safely redefine the semantics of value zero to mean "exact match". This allows to avoid some boilerplate code in PHY driver configs. Signed-off-by: Heiner Kallweit --- drivers/net/phy/phy_device.c |

[PATCH net-next 2/2] net: phy: realtek: remove boilerplate code from driver configs

2018-11-07 Thread Heiner Kallweit
After a recent change phy_id_mask value 0 means "exact match". This allows to remove setting phy_id_mask values from the driver configs. Signed-off-by: Heiner Kallweit --- drivers/net/phy/realtek.c | 9 - 1 file changed, 9 deletions(-) diff --git a/drivers/net/phy/realtek.c

[PATCH net-next] sfc: add missing NVRAM partition types for EF10

2018-11-07 Thread Edward Cree
Expose the MUM/SUC Firmware, UEFI Expansion ROM and MC Status partitions of the NIC's NVRAM as MTDs if found on the NIC. The first two are needed in order to properly update them when performing firmware updates; the MC Status partition is used to determine whether a signed firmware image was

[PATCH net-next 0/3] nfp: add and use tunnel netdev helpers

2018-11-07 Thread John Hurley
A recent patch introduced the function netif_is_vxlan() to verify the tunnel type of a given netdev as vxlan. Add a similar function to detect geneve netdevs and make use of this function in the NFP driver. Also make use of the vxlan helper where applicable. John Hurley (3): net: add

[PATCH net-next 2/3] nfp: flower: use geneve and vxlan helpers

2018-11-07 Thread John Hurley
Make use of the recently added VXLAN and geneve helper functions to determine the type of the netdev from its rtnl_link_ops. Signed-off-by: John Hurley Reviewed-by: Jakub Kicinski --- drivers/net/ethernet/netronome/nfp/flower/action.c | 8 +++- 1 file changed, 3 insertions(+), 5

[PATCH net-next 3/3] nfp: flower: include geneve as supported offload tunnel type

2018-11-07 Thread John Hurley
Offload of geneve decap rules is supported in NFP. Include geneve in the check for supported types. Signed-off-by: John Hurley Reviewed-by: Jakub Kicinski --- drivers/net/ethernet/netronome/nfp/flower/tunnel_conf.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH net-next 1/3] net: add netif_is_geneve()

2018-11-07 Thread John Hurley
Add a helper function to determine if the type of a netdev is geneve based on its rtnl_link_ops. This allows drivers that may wish to offload tunnels to check the underlying type of the device. A recent patch added a similar helper to vxlan.h Signed-off-by: John Hurley Reviewed-by: Jakub

Re: [PATCH net-next v5 8/9] ipv6: handling of multicast packets received in VRF

2018-11-07 Thread David Ahern
On 11/7/18 8:36 AM, Mike Manning wrote: > If the skb for multicast packets marked as enslaved to a VRF are > received, then the secondary device index should be used to obtain > the real device. And verify the multicast address against the > enslaved rather than the l3mdev device. > >

Re: [PATCH net-next v5 9/9] ipv6: do not drop vrf udp multicast packets

2018-11-07 Thread David Ahern
On 11/7/18 8:36 AM, Mike Manning wrote: > From: Dewi Morgan > > For bound udp sockets in a vrf, also check the sdif to get the index > for ingress devices enslaved to an l3mdev. > > Signed-off-by: Dewi Morgan > Signed-off-by: Mike Manning > --- > net/ipv6/udp.c | 8 +--- > 1 file

[PATCH bpf-next 0/2] bpftool: support loading flow dissector

2018-11-07 Thread Stanislav Fomichev
This patch series adds support for loading and attaching flow dissector programs from the bpftool: * first patch fixes flow dissector section name in the selftests (so libbpf auto-detection works) * second patch adds actual support to the bpftool See second patch for the description/details.

[PATCH bpf-next 1/2] selftests/bpf: rename flow dissector section to flow_dissector

2018-11-07 Thread Stanislav Fomichev
Makes it compatible with the logic that derives program type from section name in libbpf_prog_type_by_name. Signed-off-by: Stanislav Fomichev --- tools/testing/selftests/bpf/bpf_flow.c | 2 +- tools/testing/selftests/bpf/test_flow_dissector.sh | 2 +- 2 files changed, 2

[PATCH bpf-next 2/2] bpftool: support loading flow dissector

2018-11-07 Thread Stanislav Fomichev
This commit adds support for loading/attaching/detaching flow dissector program. The structure of the flow dissector program is assumed to be the same as in the selftests: * flow_dissector section with the main entry point * a bunch of tail call progs * a jmp_table map that is populated with the

Re: [PATCH iproute2 net-next 1/2] iplink_vxlan: Add DF configuration

2018-11-07 Thread Stefano Brivio
On Wed, 7 Nov 2018 13:03:34 -0700 David Ahern wrote: > On 11/6/18 2:39 PM, Stefano Brivio wrote: > > diff --git a/ip/iplink_vxlan.c b/ip/iplink_vxlan.c > > index 7fc0e2b4eb06..86afbe1334f0 100644 > > --- a/ip/iplink_vxlan.c > > +++ b/ip/iplink_vxlan.c > > @@ -31,6 +31,7 @@ static void

Re: [PATCH bpf-next 2/2] bpftool: support loading flow dissector

2018-11-07 Thread Jakub Kicinski
On Wed, 7 Nov 2018 20:08:53 +, Quentin Monnet wrote: > > + err = bpf_obj_pin(bpf_program__fd(prog), pinfile); > > + if (err) { > > + p_err("failed to pin program %s", > > + bpf_program__title(prog, false)); > > +

Re: [PATCH net-next 0/5] net: phy: improve and simplify phylib state machine

2018-11-07 Thread Heiner Kallweit
On 07.11.2018 21:21, Andrew Lunn wrote: > On Wed, Nov 07, 2018 at 09:05:49PM +0100, Heiner Kallweit wrote: >> On 07.11.2018 20:48, Andrew Lunn wrote: >>> On Wed, Nov 07, 2018 at 08:41:52PM +0100, Heiner Kallweit wrote: This patch series is based on two axioms: - During autoneg a PHY

[PATCH net-next 0/2] net: phy: use phy_id_mask value zero for exact match

2018-11-07 Thread Heiner Kallweit
A phy_id_mask value zero means every PHYID matches, therefore value zero isn't used. So we can safely redefine the semantics of value zero to mean "exact match". This allows to avoid some boilerplate code in PHY driver configs. Realtek PHY driver is the first user of this change. Heiner Kallweit

Re: [PATCH bpf-next 2/2] bpftool: support loading flow dissector

2018-11-07 Thread Stanislav Fomichev
On 11/07, Jakub Kicinski wrote: > On Wed, 7 Nov 2018 11:35:52 -0800, Stanislav Fomichev wrote: > > This commit adds support for loading/attaching/detaching flow > > dissector program. The structure of the flow dissector program is > > assumed to be the same as in the selftests: > > > > *

Re: [PATCH net-next] net: phy: bcm7xxx: Add entry for BCM7255

2018-11-07 Thread Andrew Lunn
On Tue, Nov 06, 2018 at 04:37:44PM -0800, Florian Fainelli wrote: > From: Justin Chen > > Add support for BCM7255 EPHY. > > Signed-off-by: Justin Chen > Signed-off-by: Florian Fainelli Reviewed-by: Andrew Lunn Andrew

Re: [PATCH net-next 0/5] net: phy: improve and simplify phylib state machine

2018-11-07 Thread Heiner Kallweit
On 07.11.2018 20:48, Andrew Lunn wrote: > On Wed, Nov 07, 2018 at 08:41:52PM +0100, Heiner Kallweit wrote: >> This patch series is based on two axioms: >> >> - During autoneg a PHY always reports the link being down > > Hi Heiner > > I think that is a risky assumption to make. > I wasn't sure

Re: [PATCH net-next 04/11] selftests: pmtu: Introduce tests for IPv4/IPv6 over VxLAN over IPv6

2018-11-07 Thread David Ahern
On 11/6/18 2:39 PM, Stefano Brivio wrote: > Use a router between endpoints, implemented via namespaces, set a low MTU > between router and destination endpoint, exceed it and check PMTU value in > route exceptions. > > Reviewed-by: Sabrina Dubroca > Signed-off-by: Stefano Brivio > --- > This

[PATCH net-next 0/5] net: phy: improve and simplify phylib state machine

2018-11-07 Thread Heiner Kallweit
This patch series is based on two axioms: - During autoneg a PHY always reports the link being down - Info in clause 22/45 registers doesn't allow to differentiate between these two states: 1. Link is physically down 2. A link partner is connected and PHY is autonegotiating In both cases

Re: [PATCH net-next 04/11] selftests: pmtu: Introduce tests for IPv4/IPv6 over VxLAN over IPv6

2018-11-07 Thread Stefano Brivio
On Wed, 7 Nov 2018 12:28:21 -0700 David Ahern wrote: > On 11/6/18 2:39 PM, Stefano Brivio wrote: > > Use a router between endpoints, implemented via namespaces, set a low MTU > > between router and destination endpoint, exceed it and check PMTU value in > > route exceptions. > > > >

[PATCH net-next 2/2] net/mlx5: Fix offsets of ifc reserved fields

2018-11-07 Thread Gal Pressman
Fix wrong offsets of reserved fields in ifc file. Issues found using pahole. Signed-off-by: Gal Pressman --- include/linux/mlx5/mlx5_ifc.h | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/include/linux/mlx5/mlx5_ifc.h b/include/linux/mlx5/mlx5_ifc.h index

[PATCH net-next 1/2] net/mlx5e: Cleanup unused defines

2018-11-07 Thread Gal Pressman
Remove couple of defines that are no longer used. Signed-off-by: Gal Pressman --- drivers/net/ethernet/mellanox/mlx5/core/en.h | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en.h b/drivers/net/ethernet/mellanox/mlx5/core/en.h index

Re: [PATCH net-next v5 6/9] vrf: mark skb for multicast or link-local as enslaved to VRF

2018-11-07 Thread David Ahern
On 11/7/18 8:36 AM, Mike Manning wrote: > The skb for packets that are multicast or to a link-local address are > not marked as being enslaved to a VRF, if they are received on a socket > bound to the VRF. This is needed for ND and it is preferable for the > kernel not to have to deal with the

Re: [PATCH net-next v5 2/9] net: ensure unbound stream socket to be chosen when not in a VRF

2018-11-07 Thread David Ahern
On 11/7/18 8:36 AM, Mike Manning wrote: > The commit a04a480d4392 ("net: Require exact match for TCP socket > lookups if dif is l3mdev") only ensures that the correct socket is > selected for packets in a VRF. However, there is no guarantee that > the unbound socket will be selected for packets

Re: [PATCH net-next v5 3/9] net: ensure unbound datagram socket to be chosen when not in a VRF

2018-11-07 Thread David Ahern
On 11/7/18 8:36 AM, Mike Manning wrote: > Ensure an unbound datagram skt is chosen when not in a VRF. The check > for a device match in compute_score() for UDP must be performed when > there is no device match. For this, a failure is returned when there is > no device match. This ensures that

Re: [PATCH net-next v5 4/9] net: provide a sysctl raw_l3mdev_accept for raw socket lookup with VRFs

2018-11-07 Thread David Ahern
On 11/7/18 8:36 AM, Mike Manning wrote: > Add a sysctl raw_l3mdev_accept to control raw socket lookup in a manner > similar to use of tcp_l3mdev_accept for stream and of udp_l3mdev_accept > for datagram sockets. Have this default to enabled for reasons of > backwards compatibility. This is so as

Re: [PATCH net-next v5 1/9] net: allow binding socket in a VRF when there's an unbound socket

2018-11-07 Thread David Ahern
On 11/7/18 8:36 AM, Mike Manning wrote: > From: Robert Shearman > > Change the inet socket lookup to avoid packets arriving on a device > enslaved to an l3mdev from matching unbound sockets by removing the > wildcard for non sk_bound_dev_if and instead relying on check against > the secondary

Re: [PATCH net-next v5 7/9] ipv6: allow ping to link-local address in VRF

2018-11-07 Thread David Ahern
On 11/7/18 8:36 AM, Mike Manning wrote: > If link-local packets are marked as enslaved to a VRF, then to allow > ping to the link-local from a vrf, the error handling for IPV6_PKTINFO > needs to be relaxed to also allow the pkt ipi6_ifindex to be that of a > slave device to the vrf. > > Note that

Re: [PATCH net-next v5 5/9] net: fix raw socket lookup device bind matching with VRFs

2018-11-07 Thread David Ahern
On 11/7/18 8:36 AM, Mike Manning wrote: > From: Duncan Eastoe > > When there exist a pair of raw sockets one unbound and one bound > to a VRF but equal in all other respects, when a packet is received > in the VRF context, __raw_v4_lookup() matches on both sockets. > > This results in the

Re: Application of f8b39039cbf2a15f ("net: fs_enet: do not call phy_stop() in interrupts") to 4.9 and 4.14 stable

2018-11-07 Thread Christophe LEROY
ping ? Le 17/10/2018 à 14:08, Christophe LEROY a écrit : Hi, Could you please apply f8b39039cbf2a15f2b8c9f081e1cbd5dee00aaf5 to 4.9 and 4.14 ? It fixes an Oops when Ethernet transmission times out. As you can observe in the commit log, the Oops what initially observed in 4.9. The fix

Re: [PATCH net-next 0/5] net: phy: improve and simplify phylib state machine

2018-11-07 Thread Andrew Lunn
On Wed, Nov 07, 2018 at 09:05:49PM +0100, Heiner Kallweit wrote: > On 07.11.2018 20:48, Andrew Lunn wrote: > > On Wed, Nov 07, 2018 at 08:41:52PM +0100, Heiner Kallweit wrote: > >> This patch series is based on two axioms: > >> > >> - During autoneg a PHY always reports the link being down > > >

Re: [PATCH net-next 0/7] nfp: more set actions and notifier refactor

2018-11-07 Thread David Miller
From: Jakub Kicinski Date: Tue, 6 Nov 2018 17:07:27 -0800 > This series brings updates to flower offload code. First Pieter adds > support for setting TTL, ToS, Flow Label and Hop Limit fields in IPv4 > and IPv6 headers. > > Remaining 5 patches deal with factoring out netdev notifiers from

Re: [PATCH bpf-next 2/2] bpftool: support loading flow dissector

2018-11-07 Thread Quentin Monnet
Hi Stanislav, 2018-11-07 11:35 UTC-0800 ~ Stanislav Fomichev > This commit adds support for loading/attaching/detaching flow > dissector program. The structure of the flow dissector program is > assumed to be the same as in the selftests: > > * flow_dissector section with the main entry point >

[net 00/14][pull request] Intel Wired LAN Driver Updates 2018-11-07

2018-11-07 Thread Jeff Kirsher
This series contains fixes to igb, i40e and ice drivers. Anirudh fixes an issue during rebuild of the ice driver, where we need to set the carrier state, as well as start or stop the queues all based on the link status. Removed functions that were duplicating current functionality in the VSI

[net 14/14] i40e: enable NETIF_F_NTUPLE and NETIF_F_HW_TC at driver load

2018-11-07 Thread Jeff Kirsher
From: Jacob Keller The assignment of the feature flag NETIF_F_NTUPLE and NETIF_F_HW_TC occurs prior to the initial setup of the local hw_features variable. This means the features are set as user-changeable, but are not set in the currently active feature list. This results in the features

[net 13/14] i40e: restore NETIF_F_GSO_IPXIP[46] to netdev features

2018-11-07 Thread Jeff Kirsher
From: Jacob Keller Since commit bacd75cfac8a ("i40e/i40evf: Add capability exchange for outer checksum", 2017-04-06) the i40e driver has not reported support for IP-in-IP offloads. This likely occurred due to a bad rebase, as the commit extracts hw_enc_features into its own variable. As part of

[net 12/14] ice: Change req_speeds to be u16

2018-11-07 Thread Jeff Kirsher
From: Chinh T Cao Since the req_speeds field in struct ice_link_status is a u8, req_speeds & ICE_AQ_LINK_SPEED_40GB always returns 0. This was caught by a coverity scan. Fix this by changing req_speeds to be u16. Reported-by: Bruce Allan Signed-off-by: Chinh T Cao Signed-off-by: Anirudh

[net 10/14] ice: Fix the bytecount sent to netdev_tx_sent_queue

2018-11-07 Thread Jeff Kirsher
From: Brett Creeley Currently if the driver does a TSO offload the bytecount sent to netdev_tx_sent_queue will be incorrect. This is because in ice_tso we overwrite the initial value that we set in ice_tx_map. This creates a mismatch between the Tx and Tx clean flow. In the Tx clean flow we

[net 09/14] ice: Fix tx_timeout in PF driver

2018-11-07 Thread Jeff Kirsher
From: Brett Creeley Prior to this commit the driver was running into tx_timeouts when a queue was stressed enough. This was happening because the HW tail and SW tail (NTU) were incorrectly out of sync. Consequently this was causing the HW head to collide with the HW tail, which to the hardware

[net 11/14] igb: shorten maximum PHC timecounter update interval

2018-11-07 Thread Jeff Kirsher
From: Miroslav Lichvar The timecounter needs to be updated at least once per ~550 seconds in order to avoid a 40-bit SYSTIM timestamp to be misinterpreted as an old timestamp. Since commit 500462a9de65 ("timers: Switch to a non-cascading wheel"), scheduling of delayed work seems to be less

[net 07/14] ice: Fix typo in error message

2018-11-07 Thread Jeff Kirsher
From: Anirudh Venkataramanan Print should say "Enabling" instead of "Enaabling" Signed-off-by: Akeem G Abodunrin Signed-off-by: Anirudh Venkataramanan Tested-by: Andrew Bowers Signed-off-by: Jeff Kirsher --- drivers/net/ethernet/intel/ice/ice_lib.c | 2 +- 1 file changed, 1 insertion(+), 1

[net 06/14] ice: Fix flags for port VLAN

2018-11-07 Thread Jeff Kirsher
From: Md Fahad Iqbal Polash According to the spec, whenever insert PVID field is set, the VLAN driver insertion mode should be set to 01b which isn't done currently. Fix it. Signed-off-by: Md Fahad Iqbal Polash Signed-off-by: Anirudh Venkataramanan Tested-by: Andrew Bowers Signed-off-by:

[net 05/14] ice: Remove duplicate addition of VLANs in replay path

2018-11-07 Thread Jeff Kirsher
From: Anirudh Venkataramanan ice_restore_vlan and active_vlans were originally put in place to reprogram VLAN filters in the replay path. This is now done as part of the much broader VSI rebuild/replay framework. So remove both ice_restore_vlan and active_vlans Signed-off-by: Anirudh

[net 03/14] ice: Fix dead device link issue with flow control

2018-11-07 Thread Jeff Kirsher
From: Akeem G Abodunrin Setting Rx or Tx pause parameter currently results in link loss on the interface, requiring the platform/host to be cold power cycled. Fix it. Signed-off-by: Akeem G Abodunrin Signed-off-by: Anirudh Venkataramanan Tested-by: Andrew Bowers Signed-off-by: Jeff Kirsher

[net 08/14] ice: Fix napi delete calls for remove

2018-11-07 Thread Jeff Kirsher
From: Dave Ertman In the remove path, the vsi->netdev is being set to NULL before the call to free vectors. This is causing the netif_napi_del call to never be made. Add a call to ice_napi_del to the same location as the calls to unregister_netdev and just prior to them. This will use the

[net 04/14] ice: Free VSI contexts during for unload

2018-11-07 Thread Jeff Kirsher
From: Victor Raj In the unload path, all VSIs are freed. Also free the related VSI contexts to prevent memory leaks. Signed-off-by: Victor Raj Signed-off-by: Anirudh Venkataramanan Tested-by: Andrew Bowers Signed-off-by: Jeff Kirsher --- drivers/net/ethernet/intel/ice/ice_common.c | 3 +++

[net 01/14] ice: Set carrier state and start/stop queues in rebuild

2018-11-07 Thread Jeff Kirsher
From: Anirudh Venkataramanan Set the carrier state post rebuild by querying the link status. Also start/stop queues based on link status. Signed-off-by: Anirudh Venkataramanan Tested-by: Andrew Bowers Signed-off-by: Jeff Kirsher --- drivers/net/ethernet/intel/ice/ice_main.c | 18

[net 02/14] ice: Check for reset in progress during remove

2018-11-07 Thread Jeff Kirsher
From: Anirudh Venkataramanan The remove path does not currently check to see if a reset is in progress before proceeding. This can cause a resource collision resulting in various types of errors. Check for reset in progress and wait for a reasonable amount of time before allowing the remove to

Re: [PATCH net-next 04/11] selftests: pmtu: Introduce tests for IPv4/IPv6 over VxLAN over IPv6

2018-11-07 Thread David Miller
From: David Ahern Date: Wed, 7 Nov 2018 12:28:21 -0700 > you can add them now and wrapped in a 'does ip support the df option' > check. That is needed regardless of order (kernel vs iproute2). Indeed, that's a good point.

[PATCH net-next 1/5] net: phy: remove useless check in state machine case PHY_NOLINK

2018-11-07 Thread Heiner Kallweit
If aneg is enabled and the PHY reports the link as up then definitely aneg finished successfully. Therefore this check is useless and can be removed. Signed-off-by: Heiner Kallweit --- drivers/net/phy/phy.c | 11 --- 1 file changed, 11 deletions(-) diff --git a/drivers/net/phy/phy.c

Re: [PATCH bpf-next 2/2] bpftool: support loading flow dissector

2018-11-07 Thread Jakub Kicinski
On Wed, 7 Nov 2018 13:00:09 -0800, Stanislav Fomichev wrote: > > > + } > > > + > > > + if (attr.prog_type == BPF_PROG_TYPE_FLOW_DISSECTOR) { > > > + err = build_flow_dissector_jmp_table(obj, prog, "jmp_table"); > > > + if (err) { > > > + p_err("failed to build flow

Re: [PATCH bpf] bpf: Fix IPv6 dport byte order in bpf_sk_lookup_udp

2018-11-07 Thread Martin Lau
On Wed, Nov 07, 2018 at 01:36:07PM -0800, Andrey Ignatov wrote: > Lookup functions in sk_lookup have different expectations about byte > order of provided arguments. > > Specifically __inet_lookup, __udp4_lib_lookup and __udp6_lib_lookup > expect dport to be in network byte order and do

[PATCH ipsec-next 04/11] xfrm: policy: return NULL when inexact search needed

2018-11-07 Thread Florian Westphal
currently policy_hash_bysel() returns the hash bucket list (for exact policies), or the inexact list (when policy uses a prefix). Searching this inexact list is slow, so it might be better to pre-sort inexact lists into a tree or another data structure for faster searching. However, due to 'any'

[PATCH bpf-next 3/3] bpftool: support loading flow dissector

2018-11-07 Thread Stanislav Fomichev
This commit adds support for loading/attaching/detaching flow dissector program. The structure of the flow dissector program is assumed to be the same as in the selftests: * flow_dissector section with the main entry point * a bunch of tail call progs * a jmp_table map that is populated with the

[PATCH v2 bpf-next 0/3] bpftool: support loading flow dissector

2018-11-07 Thread Stanislav Fomichev
v2 changes: * addressed comments/style issues from Jakub Kicinski & Quentin Monnet * removed logic that populates jump table * added cleanup for partial failure in bpf_object__pin This patch series adds support for loading and attaching flow dissector programs from the bpftool: * first patch

[PATCH bpf-next 2/3] libbpf: cleanup after partial failure in bpf_object__pin

2018-11-07 Thread Stanislav Fomichev
bpftool will use bpf_object__pin in the next commit to pin all programs and maps from the file; in case of a partial failure, we need to get back to the clean state (undo previous program/map pins). Signed-off-by: Stanislav Fomichev --- tools/lib/bpf/libbpf.c | 58

[PATCH bpf-next 1/3] selftests/bpf: rename flow dissector section to flow_dissector

2018-11-07 Thread Stanislav Fomichev
Makes it compatible with the logic that derives program type from section name in libbpf_prog_type_by_name. Signed-off-by: Stanislav Fomichev --- tools/testing/selftests/bpf/bpf_flow.c | 2 +- tools/testing/selftests/bpf/test_flow_dissector.sh | 2 +- 2 files changed, 2

Re: [PATCH bpf-next 2/3] libbpf: cleanup after partial failure in bpf_object__pin

2018-11-07 Thread Jakub Kicinski
On Wed, 7 Nov 2018 14:43:55 -0800, Stanislav Fomichev wrote: > bpftool will use bpf_object__pin in the next commit to pin all programs > and maps from the file; in case of a partial failure, we need to get > back to the clean state (undo previous program/map pins). > > Signed-off-by: Stanislav

Re: [PATCH bpf-next 3/3] bpftool: support loading flow dissector

2018-11-07 Thread Stanislav Fomichev
On 11/07, Jakub Kicinski wrote: > On Wed, 7 Nov 2018 15:13:33 -0800, Stanislav Fomichev wrote: > > On 11/07, Jakub Kicinski wrote: > > > On Wed, 7 Nov 2018 14:43:56 -0800, Stanislav Fomichev wrote: > > > > bpftool map update pinned /sys/fs/bpf/flow/jmp_table \ > > > > key 0 0 0 0 \ > >

Re: [PATCH bpf-next 3/3] bpftool: support loading flow dissector

2018-11-07 Thread Stanislav Fomichev
On 11/07, Jakub Kicinski wrote: > On Wed, 7 Nov 2018 15:34:48 -0800, Stanislav Fomichev wrote: > > On 11/07, Jakub Kicinski wrote: > > > On Wed, 7 Nov 2018 15:13:33 -0800, Stanislav Fomichev wrote: > > > > On 11/07, Jakub Kicinski wrote: > > > > > On Wed, 7 Nov 2018 14:43:56 -0800, Stanislav

Re: [PATCH bpf] tools/bpftool: copy uapi/linux/tc_act/tc_bpf.h to tools directory

2018-11-07 Thread Li Zhijian
On 11/8/2018 9:00 AM, Yonghong Song wrote: Commit f6f3bac08ff9 ("tools/bpf: bpftool: add net support") added certain networking support to bpftool. The implementation relies on a relatively recent uapi header file linux/tc_act/tc_bpf.h on the host which contains the marco definition of

[PATCH net-next 3/7] net: sched: set TCQ_F_OFFLOADED flag for MQ

2018-11-07 Thread Jakub Kicinski
PRIO and RED mark the qdisc with TCQ_F_OFFLOADED upon successful offload, make MQ do the same. The consistency will help with consistent graft callback behaviour. Signed-off-by: Jakub Kicinski Reviewed-by: John Hurley --- net/sched/sch_mq.c | 9 +++-- 1 file changed, 3 insertions(+), 6

[PATCH net-next 4/7] net: sched: add an offload graft helper

2018-11-07 Thread Jakub Kicinski
Qdisc graft operation of offload-capable qdiscs performs a few extra steps which are identical among all the qdiscs. Add a helper to share this code. Signed-off-by: Jakub Kicinski Reviewed-by: John Hurley --- include/net/sch_generic.h | 12 net/sched/sch_api.c | 29

[PATCH net-next 7/7] net: sched: prio: delay destroying child qdiscs on change

2018-11-07 Thread Jakub Kicinski
Move destroying of the old child qdiscs outside of the sch_tree_lock() section. This should improve the software qdisc replace but is even more important for offloads. Calling offloads under a spin lock is best avoided, and child's destroy would be called under sch_tree_lock(). Signed-off-by:

[PATCH net-next 5/7] net: sched: refactor grafting Qdiscs with a parent

2018-11-07 Thread Jakub Kicinski
The code for grafting Qdiscs when there is a parent has two needless indentation levels, and breaks the "keep the success path unindented" guideline. Refactor. Signed-off-by: Jakub Kicinski Reviewed-by: John Hurley --- net/sched/sch_api.c | 28 ++-- 1 file changed, 14

[PATCH net-next 1/7] net: sched: add an offload dump helper

2018-11-07 Thread Jakub Kicinski
Qdisc dump operation of offload-capable qdiscs performs a few extra steps which are identical among all the qdiscs. Add a helper to share this code. Signed-off-by: Jakub Kicinski Reviewed-by: John Hurley --- include/net/sch_generic.h | 12 net/sched/sch_api.c | 21

[PATCH net-next 0/7] net: sched: prepare for more Qdisc offloads

2018-11-07 Thread Jakub Kicinski
Hi! This series refactors the "switchdev" Qdisc offloads a little. We have a few Qdiscs which can be fully offloaded today to the forwarding plane of switching devices. First patch adds a helper for handing statistic dumps, the code seems to be copy pasted between PRIO and RED. Second patch

[PATCH net-next 2/7] net: sched: red: remove unnecessary red_dump_offload_stats parameter

2018-11-07 Thread Jakub Kicinski
Offload dump helper does not use opt parameter, remove it. Signed-off-by: Jakub Kicinski Reviewed-by: John Hurley --- net/sched/sch_red.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/net/sched/sch_red.c b/net/sched/sch_red.c index d5e441194397..2bf1d2fabc48 100644

Re: [Kernel][NET] Bug report on packet defragmenting

2018-11-07 Thread Eric Dumazet
On 11/07/2018 05:29 PM, 배석진 wrote: > If ipv6_defrag hook is not excuted simultaneously, then it's ok. > ipv6_defrag hook can handle that. [exam 3] This seems wrong. This is the root cause, we should not try to work around it but fix it. There is no guarantee that RSS/RPS/RFS can help here,

Re: [PATCH bpf-next] xdp: sample code for redirecting vlan packets to specific cpus

2018-11-07 Thread Daniel Borkmann
On 10/29/2018 11:11 PM, John Fastabend wrote: > On 10/29/2018 02:19 PM, Shannon Nelson wrote: >> This is an example of using XDP to redirect the processing of >> particular vlan packets to specific CPUs. This is in response >> to comments received on a kernel patch put forth previously >> to do

[PATCH net-next] sock: Reset dst when changing sk_mark via setsockopt

2018-11-07 Thread David Barmann
When setting the SO_MARK socket option, the dst needs to be reset so that a new route lookup is performed. This fixes the case where an application wants to change routing by setting a new sk_mark. If this is done after some packets have already been sent, the dst is cached and has no effect.

Re: [PATCH bpf-next 2/3] libbpf: cleanup after partial failure in bpf_object__pin

2018-11-07 Thread Stanislav Fomichev
On 11/07, Jakub Kicinski wrote: > On Wed, 7 Nov 2018 14:43:55 -0800, Stanislav Fomichev wrote: > > bpftool will use bpf_object__pin in the next commit to pin all programs > > and maps from the file; in case of a partial failure, we need to get > > back to the clean state (undo previous

Re: [PATCH bpf-next 3/3] bpftool: support loading flow dissector

2018-11-07 Thread Stanislav Fomichev
On 11/07, Jakub Kicinski wrote: > On Wed, 7 Nov 2018 14:43:56 -0800, Stanislav Fomichev wrote: > > bpftool map update pinned /sys/fs/bpf/flow/jmp_table \ > > key 0 0 0 0 \ > > value pinned /sys/fs/bpf/flow/IP/0 > > Where is that /0 coming from ? Is that in source code? I don't

[PATCH iproute2] bridge: fdb: remove redundant dev string in show output

2018-11-07 Thread Roopa Prabhu
From: Roopa Prabhu After commit 4abb8c723a64 ("bridge: fdb: Fix for missing keywords in non-JSON output"), I am seeing a double print for dev in bridge fdb show. eg: "44:38:39:00:6a:82 dev dev bridge vlan 1 master bridge permanent" this patch removes the redundant print. Fixes: 4abb8c723a64

Re: [PATCH bpf-next 2/2] bpftool: support loading flow dissector

2018-11-07 Thread Stanislav Fomichev
On 11/07, Jakub Kicinski wrote: > On Wed, 7 Nov 2018 14:15:06 -0800, Stanislav Fomichev wrote: > > On 11/07, Quentin Monnet wrote: > > > 2018-11-07 12:32 UTC-0800 ~ Jakub Kicinski > > > > > > > On Wed, 7 Nov 2018 20:08:53 +, Quentin Monnet wrote: > > > > > > + err =

Re: [PATCH bpf] tools/bpftool: copy uapi/linux/tc_act/tc_bpf.h to tools directory

2018-11-07 Thread Yonghong Song
On 11/7/18 5:15 PM, Li Zhijian wrote: > On 11/8/2018 9:00 AM, Yonghong Song wrote: >> Commit f6f3bac08ff9 ("tools/bpf: bpftool: add net support") >> added certain networking support to bpftool. >> The implementation relies on a relatively recent uapi header file >> linux/tc_act/tc_bpf.h on the

[PATCH bpf] bpf: Fix IPv6 dport byte order in bpf_sk_lookup_udp

2018-11-07 Thread Andrey Ignatov
Lookup functions in sk_lookup have different expectations about byte order of provided arguments. Specifically __inet_lookup, __udp4_lib_lookup and __udp6_lib_lookup expect dport to be in network byte order and do ntohs(dport) internally. At the same time __inet6_lookup expects dport to be in

Re: [PATCH bpf-next 2/3] libbpf: cleanup after partial failure in bpf_object__pin

2018-11-07 Thread Jakub Kicinski
On Wed, 7 Nov 2018 15:00:21 -0800, Stanislav Fomichev wrote: > > > +err_unpin_programs: > > > + bpf_object__for_each_program(prog, obj) { > > > + char buf[PATH_MAX]; > > > + int len; > > > + > > > + len = snprintf(buf, PATH_MAX, "%s/%s", path, > > > +

Re: [PATCH net-next 00/10] udp: implement GRO support

2018-11-07 Thread David Miller
From: Paolo Abeni Date: Wed, 7 Nov 2018 12:38:27 +0100 > This series implements GRO support for UDP sockets, as the RX counterpart > of commit bec1f6f69736 ("udp: generate gso with UDP_SEGMENT"). > The core functionality is implemented by the second patch, introducing a new > sockopt to enable

Re: [PATCH bpf-next 2/2] bpftool: support loading flow dissector

2018-11-07 Thread Stanislav Fomichev
On 11/07, Quentin Monnet wrote: > Hi Stanislav, > > 2018-11-07 11:35 UTC-0800 ~ Stanislav Fomichev > > This commit adds support for loading/attaching/detaching flow > > dissector program. The structure of the flow dissector program is > > assumed to be the same as in the selftests: > > > > *

Re: [PATCH bpf-next 2/3] libbpf: cleanup after partial failure in bpf_object__pin

2018-11-07 Thread Stanislav Fomichev
On 11/07, Jakub Kicinski wrote: > On Wed, 7 Nov 2018 15:00:21 -0800, Stanislav Fomichev wrote: > > > > +err_unpin_programs: > > > > + bpf_object__for_each_program(prog, obj) { > > > > + char buf[PATH_MAX]; > > > > + int len; > > > > + > > > > + len =

[PATCH V2 bpf-next 2/2] selftests/bpf: add a test case for sock_ops perf-event notification

2018-11-07 Thread Sowmini Varadhan
This patch provides a tcp_bpf based eBPF sample. The test - ncat(1) as the TCP client program to connect() to a port with the intention of triggerring SYN retransmissions: we first install an iptables DROP rule to make sure ncat SYNs are resent (instead of aborting instantly after a TCP RST)

[PATCH V2 bpf-next 1/2] bpf: add perf-event notificaton support for sock_ops

2018-11-07 Thread Sowmini Varadhan
This patch allows eBPF programs that use sock_ops to send perf-based event notifications using bpf_perf_event_output() Signed-off-by: Sowmini Varadhan --- net/core/filter.c | 19 +++ 1 files changed, 19 insertions(+), 0 deletions(-) diff --git a/net/core/filter.c

[PATCH V2 bpf-next 0/2] Perf-based event notification for sock_ops

2018-11-07 Thread Sowmini Varadhan
This patchset uses eBPF perf-event based notification mechanism to solve the problem described in https://marc.info/?l=linux-netdev=154022219423571=2. Thanks to Daniel Borkmann for feedback/input. V2: inlined the call to sys_perf_event_open() following the style of existing code in

Re: [net-next PATCH] net: sched: cls_flower: Classify packets using port ranges

2018-11-07 Thread Nambiar, Amritha
On 10/19/2018 1:52 AM, Jiri Pirko wrote: > Thu, Oct 18, 2018 at 08:24:44PM CEST, amritha.namb...@intel.com wrote: >> On 10/18/2018 5:17 AM, Jiri Pirko wrote: >>> Fri, Oct 12, 2018 at 03:53:30PM CEST, amritha.namb...@intel.com wrote: Added support in tc flower for filtering based on port

  1   2   3   >