Re: [RFC PATCH] perf, bpf: Retain kernel executable code in memory to aid Intel PT tracing

2019-02-10 Thread Adrian Hunter
On 9/02/19 1:29 AM, Alexei Starovoitov wrote: > On Thu, Feb 07, 2019 at 01:19:01PM +0200, Adrian Hunter wrote: >> Subject to memory pressure and other limits, retain executable code, such >> as JIT-compiled bpf, in memory instead of freeing it immediately it is no >> longer needed for execution. >>

[PATCH net-next 1/1] flow_offload: Fix flow action infrastructure

2019-02-10 Thread Eli Britstein
Implementation of macro "flow_action_for_each" introduced in commit e3ab786b42535 ("flow_offload: add flow action infrastructure") and used in commit 738678817573c ("drivers: net: use flow action infrastructure") iterated the first item twice and did not reach the last one. Fix it. Fixes: e3ab786b

Re: [PATCH bpf-next v4 0/2] libbpf: adding AF_XDP support

2019-02-10 Thread Magnus Karlsson
On Mon, Feb 11, 2019 at 7:34 AM Jean-Mickael Guerin wrote: > > Hi Magnus, > > > * In a future release, I am planning on adding a higher level data > > plane interface too. This will be based around recvmsg and sendmsg > > with the use of struct iovec for batching, without the user having > >

Re: [PATCH net-next v2 00/10] net: phy: Add support for 2.5GBASET PHYs

2019-02-10 Thread Maxime Chevallier
Hello Heiner, >Hi Maxime, > >Andrew and me are working on Aquantia PHY support and he handed over >to me a patch series which includes parts of the first version of your >series. Having said that I'm especially interested in your patches >5 and 6. Because your series is somewhat bigger and there a

Re: [PATCH net-next 0/2] Revert wake_on_lan devlink parameter

2019-02-10 Thread David Miller
From: Vasundhara Volam Date: Mon, 11 Feb 2019 10:09:23 +0530 > On Sat, Feb 9, 2019 at 12:37 PM David Miller wrote: >> >> From: Vasundhara Volam >> Date: Fri, 8 Feb 2019 14:43:08 +0530 >> >> > As per discussion with Jakub Kicinski and Michal Kubecek, >> > this will be better addressed by soon-t

Re: [Patch net 2/3] net_sched: fix a memory leak in cls_tcindex

2019-02-10 Thread Cong Wang
On Sun, Feb 10, 2019 at 6:15 PM kbuild test robot wrote: > > Hi Cong, > > I love your patch! Yet something to improve: > > [auto build test ERROR on net/master] > > url: > https://github.com/0day-ci/linux/commits/Cong-Wang/net_sched-some-fixes-for-cls_tcindex/20190211-095057 > config: i386-ran

[RFC 3/3] nfp: devlink: allow flashing the device via devlink

2019-02-10 Thread Jakub Kicinski
Devlink now allows updating device flash. Implement this callback. Compared to ethtool update we no longer have to release the networking locks - devlink doesn't take them. Signed-off-by: Jakub Kicinski --- .../net/ethernet/netronome/nfp/nfp_devlink.c | 9 drivers/net/ethernet/netronome

[RFC 2/3] ethtool: add compat for flash update

2019-02-10 Thread Jakub Kicinski
If driver does not support ethtool flash update operation call into devlink. Signed-off-by: Jakub Kicinski --- include/net/devlink.h | 9 + net/core/devlink.c| 31 +++ net/core/ethtool.c| 12 +--- 3 files changed, 49 insertions(+), 3 deletions

[RFC 1/3] devlink: add flash update command

2019-02-10 Thread Jakub Kicinski
Add devlink flash update command. Advanced NICs have firmware stored in flash and often cryptographically secured. Updating that flash is handled by management firmware. Ethtool has a flash update command which served us well, however, it has two shortcomings: - it takes rtnl_lock unnecessarily -

[RFC iproute2] devlink: add support for updating device flash

2019-02-10 Thread Jakub Kicinski
Add new command for updating flash of devices via devlink API. Example: $ cp flash-boot.bin /lib/firmware/ $ devlink dev flash pci/:05:00.0 file flash-boot.bin Signed-off-by: Jakub Kicinski --- devlink/devlink.c | 54 ++ man/man8/devlink-dev.8 |

[RFC 0/3] devlink: add the ability to update device flash

2019-02-10 Thread Jakub Kicinski
Hi! This series is the second step to allow trouble shooting and recovering devices in bad state without the use of netdevs as handles. We can already query FW versions over devlink, now we add the ability to update the FW. This will allow drivers to implement some from of "limp-mode" where the

[net] tipc: fix link session and re-establish issues

2019-02-10 Thread Tuong Lien
When a link endpoint is re-created (e.g. after a node reboot or interface reset), the link session number is varied by random, the peer endpoint will be synced with this new session number before the link is re-established. However, there is a shortcoming in this mechanism that can lead to the lin

Re: [PATCH bpf-next v4 0/2] libbpf: adding AF_XDP support

2019-02-10 Thread Jean-Mickael Guerin
Hi Magnus, > * In a future release, I am planning on adding a higher level data > plane interface too. This will be based around recvmsg and sendmsg > with the use of struct iovec for batching, without the user having > to know anything about the underlying four rings of an AF_XDP > socket

[PATCH] Documentation: fix some freescale dpio-driver.rst warnings

2019-02-10 Thread Randy Dunlap
From: Randy Dunlap Fix markup warnings for one list by using correct list syntax. Fix markup warnings for another list by using blank lines before the list. Documentation/networking/device_drivers/freescale/dpaa2/dpio-driver.rst:30: WARNING: Unexpected indentation. Documentation/networking/devi

Re: r8169 Driver - Poor Network Performance Since Kernel 4.19

2019-02-10 Thread David Chang
Hi Heiner, Sorry for late! On Feb 05, 2019 at 19:50:30 +0100, Heiner Kallweit wrote: > Hi David, > > meanwhile there's the following bug report matching what reported. > It's even the same chip version (RTL8168h). > https://bugzilla.redhat.com/show_bug.cgi?id=1671958 > > Symptom there is also a

Re: [PATCH net-next 0/2] Revert wake_on_lan devlink parameter

2019-02-10 Thread Vasundhara Volam
On Sat, Feb 9, 2019 at 12:37 PM David Miller wrote: > > From: Vasundhara Volam > Date: Fri, 8 Feb 2019 14:43:08 +0530 > > > As per discussion with Jakub Kicinski and Michal Kubecek, > > this will be better addressed by soon-too-come ethtool netlink > > API with additional indication that given W

Re: [PATCH bpf] xsk: add missing smp_rmb() in xsk_mmap

2019-02-10 Thread Alexei Starovoitov
On Fri, Feb 08, 2019 at 02:13:50PM +0100, Magnus Karlsson wrote: > All the setup code in AF_XDP is protected by a mutex with the > exception of the mmap code that cannot use it. To make sure that a > process banging on the mmap call at the same time as another process > is setting up the socket, sm

Re: [PATCH bpf-next 3/3] selftests: bpf: centre kernel bpf objects under new subdir "kern_progs"

2019-02-10 Thread Alexei Starovoitov
On Fri, Feb 08, 2019 at 05:41:21PM +, Jiong Wang wrote: > At the moment, all kernel bpf objects are listed under BPF_OBJ_FILES. > Listing them manually sometimes causing patch conflict when people are > adding new testcases simultaneously. > > It is better to centre all the related source file

Re: [PATCH bpf-next 2/3] selftests: bpf: extend sub-register mode compilation to all bpf object files

2019-02-10 Thread Alexei Starovoitov
On Fri, Feb 08, 2019 at 05:41:20PM +, Jiong Wang wrote: > At the moment, we only do extra sub-register mode compilation on bpf object > files used by "test_progs". These object files are really loaded and > executed. > > This patch further extends sub-register mode compilation to all bpf objec

Re: [PATCH bpf] bpf: only adjust gso_size on bytestream protocols

2019-02-10 Thread Alexei Starovoitov
On Thu, Feb 07, 2019 at 02:54:16PM -0500, Willem de Bruijn wrote: > From: Willem de Bruijn > > bpf_skb_change_proto and bpf_skb_adjust_room change skb header length. > For GSO packets they adjust gso_size to maintain the same MTU. > > The gso size can only be safely adjusted on bytestream protoc

[PATCH net-next v3] ipmr: ip6mr: Create new sockopt to clear mfc cache or vifs

2019-02-10 Thread Callum Sinclair
Created a way to clear the multicast forwarding cache on a socket without having to either remove the entries manually using the delete entry socket option or destroy and recreate the multicast socket. Calling the socket option MRT_FLUSH will allow any combination of the four flag options to be cl

Re: [PATCH v2 bpf-next 0/7] Add __sk_buff->sk, bpf_tcp_sock, BPF_FUNC_tcp_sock and BPF_FUNC_sk_fullsock

2019-02-10 Thread Alexei Starovoitov
On Sat, Feb 09, 2019 at 11:22:20PM -0800, Martin KaFai Lau wrote: > This series adds __sk_buff->sk, "struct bpf_tcp_sock", > BPF_FUNC_sk_fullsock and BPF_FUNC_tcp_sock. Together, they provide > a common way to expose the members of "struct tcp_sock" and > "struct bpf_sock" for the bpf_prog to acce

[PATCH net-next v3] ipmr: ip6mr: Create new sockopt to clear mfc cache or vifs

2019-02-10 Thread Callum Sinclair
v1 -> v2: Implemented additional flags for static entries v2 -> v3: Cleaned up flag logic so any combination of routes can be cleared. Fixed style errors Fixed incorrect flag values Currently the only way to clear the forwarding cache was to delete the entries one by one using the MRT_DEL_MFC sock

Re: [PATCH bpf] bpf: Fix narrow load on a bpf_sock returned from sk_lookup()

2019-02-10 Thread Alexei Starovoitov
On Sun, Feb 10, 2019 at 07:15:17AM +, Martin Lau wrote: > > > Fixes: c64b7983288e ("bpf: Add PTR_TO_SOCKET verifier type") > > > Cc: Joe Stringer > > > Signed-off-by: Martin KaFai Lau > > > > Applied to bpf tree. > Thanks! > > > > > Martin, if your is_fullsock work depends on it, I can app

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

2019-02-10 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the phy-next tree got conflicts in: drivers/phy/marvell/Kconfig drivers/phy/marvell/Makefile between commit: 14dc100b4411 ("phy: armada38x: add common phy support") from the net-next tree and commit: 9695375a3f4a ("phy: add A3700 COMPHY support")

[PATCH net-next v2 4/5] nfp: devlink: use the generic manufacture identifier instead of vendor

2019-02-10 Thread Jakub Kicinski
Vendor may sound ambiguous, let's rename the fab string to "board.manufacture" (which was just added as a generic identifier). Signed-off-by: Jakub Kicinski Reviewed-by: Dirk van der Merwe --- drivers/net/ethernet/netronome/nfp/nfp_devlink.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH net-next v2 5/5] nfp: devlink: include vendor/product info in serial number

2019-02-10 Thread Jakub Kicinski
The manufacturing team requests we include vendor and product in the serial number field, as the serial number itself is not unique across manufacturing facilities and products. Signed-off-by: Jakub Kicinski Reviewed-by: Dirk van der Merwe --- .../net/ethernet/netronome/nfp/nfp_devlink.c | 21

[PATCH net-next v2 0/5] devlink: minor tweaks to reported device info

2019-02-10 Thread Jakub Kicinski
Hi! This series contains two minor touch ups for devlink code. First || is corrected to && in the ethtool compat code. Next patch decreases the stack allocation size. On the nfp side after further discussions with the manufacturing team we decided to realign the serial number contents slightly an

[PATCH net-next v2 2/5] devlink: don't allocate attrs on the stack

2019-02-10 Thread Jakub Kicinski
Number of devlink attributes has grown over 128, causing the following warning: ../net/core/devlink.c: In function ‘devlink_nl_cmd_region_read_dumpit’: ../net/core/devlink.c:3740:1: warning: the frame size of 1064 bytes is larger than 1024 bytes [-Wframe-larger-than=] } ^ Since the number of

[PATCH net-next v2 3/5] devlink: add a generic board.manufacture version name

2019-02-10 Thread Jakub Kicinski
At Jiri's suggestion add a generic "board.manufacture" version identifier. Signed-off-by: Jakub Kicinski --- Documentation/networking/devlink-info-versions.rst | 5 + include/net/devlink.h | 2 ++ 2 files changed, 7 insertions(+) diff --git a/Documentation/netwo

[PATCH net-next v2 1/5] devlink: fix condition for compat device info

2019-02-10 Thread Jakub Kicinski
We need the port to be both ethernet and have the rigth netdev, not one or the other. Fixes: ddb6e99e2db1 ("ethtool: add compat for devlink info") Signed-off-by: Jakub Kicinski Acked-by: Jiri Pirko --- net/core/devlink.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/co

Re: [PATCH net-next v5 09/12] socket: Add SO_TIMESTAMPING_NEW

2019-02-10 Thread Deepa Dinamani
On Feb 10, 2019, at 7:43 AM, Ran Rozenstein wrote: >> Subject: [PATCH net-next v5 09/12] socket: Add SO_TIMESTAMPING_NEW >> >> Add SO_TIMESTAMPING_NEW variant of socket timestamp options. >> This is the y2038 safe versions of the SO_TIMESTAMPING_OLD for all >> architectures. >> >> Signed-off-by:

Re: [RFC] apparently bogus logics in unix_find_other() since 2002

2019-02-10 Thread Al Viro
On Sun, Feb 10, 2019 at 04:24:15AM +, Al Viro wrote: > > Looks like that should be impossible; what am I missing here? Incidentally, > how can the quoted fragment in in unix_stream_connect() be reached with NULL > otheru->addr? After all, otheru is unix_sock of a listener; how could > we pos

Re: [PATCH iproute2-next] use print_{,h}hu instead of print_uint when format specifier is %{,h}hu

2019-02-10 Thread David Ahern
On 2/7/19 3:51 AM, Davide Caratti wrote: > in this way, a useless cast to unsigned int is avoided in bpf_print_ops() > and print_tunnel(). > > Tested with: > # ./tdc.py -c bpf > > Suggested-by: Stephen Hemminger > Cc: Andrea Claudi > Signed-off-by: Davide Caratti > --- > ip/ipl2tp.c | 4 ++--

Re: [PATCH v3] arm64: dts: lx2160aqds: Add mdio mux nodes

2019-02-10 Thread Shawn Guo
On Wed, Feb 06, 2019 at 09:40:33AM +, Pankaj Bansal wrote: > The two external MDIO buses used to communicate with phy devices that are > external to SOC are muxed in LX2160AQDS board. > > These buses can be routed to any one of the eight IO slots on LX2160AQDS > board depending on value in fpg

[PATCH v2] net: fix IPv6 prefix route residue

2019-02-10 Thread Zhiqiang Liu
From: Zhiqiang Liu Follow those steps: # ip addr add 2001:123::1/32 dev eth0 # ip addr add 2001:123:456::2/64 dev eth0 # ip addr del 2001:123::1/32 dev eth0 # ip addr del 2001:123:456::2/64 dev eth0 and then prefix route of 2001:123::1/32 will still exist. This is because ipv6_prefix_equal i

Re: [PATCH net-next 3/4] nfp: devlink: rename vendor to manufacture

2019-02-10 Thread Jakub Kicinski
On Sat, 9 Feb 2019 09:36:44 +0100, Jiri Pirko wrote: > >+{ "board.manufacture", "assembly.vendor", }, > > I wonder, why this is not among generic? No real reason, I'll move it in v2.

Re: [PATCH for-next 1/4] devlink: refactor validation of finding required arguments

2019-02-10 Thread David Ahern
On 2/10/19 11:28 AM, Aya Levin wrote: > @@ -950,6 +951,51 @@ static int param_cmode_get(const char *cmodestr, > return 0; > } > > +struct dl_args_metadata { > + uint32_t o_flag; > + char err_msg[DL_ARGS_REQUIRED_MAX_ERR_LEN]; > +}; > + > +static const struct dl_args_metadata dl_arg

Re: [PATCH for-next 2/4] devlink: fix print of uint64_t

2019-02-10 Thread David Ahern
On 2/10/19 1:34 PM, Stephen Hemminger wrote: > On Sun, 10 Feb 2019 20:28:47 +0200 > Aya Levin wrote: > >> This patch prints uint64_t with its corresponding format and avoid implicit >> cast to uint32_t. >> >> Signed-off-by: Aya Levin >> Reviewed-by: Moshe Shemesh >> Reported-by: Maria Pasechn

Re: [PATCH] net: fix IPv6 prefix route residue

2019-02-10 Thread Zhiqiang Liu
> On 2/3/19 9:04 AM, David Miller wrote: >> From: Zhiqiang Liu >> Date: Sun, 3 Feb 2019 14:10:31 +0800 >> >>> @@ -1165,7 +1165,8 @@ enum cleanup_prefix_rt_t { >>> list_for_each_entry(ifa, &idev->addr_list, if_list) { >>> if (ifa == ifp) >>> continue; >>> -

[net] tipc: fix skb may be leaky in tipc_link_input

2019-02-10 Thread Hoang Le
When we free skb at tipc_data_input, we return a 'false' boolean. Then, skb passed to subcalling tipc_link_input in tipc_link_rcv, 1303 int tipc_link_rcv: ... 1354if (!tipc_data_input(l, skb, l->inputq)) 1355rc |= tipc_link_input(l, skb, l->inputq); Fix it by simple changing to a 't

[PATCH] mt76: change the retun type of mt76_dma_attach()

2019-02-10 Thread Ryder Lee
There is no need to retun 0 in mt76_dma_attach(), so switch it to void. Signed-off-by: Ryder Lee --- drivers/net/wireless/mediatek/mt76/dma.c | 3 +-- drivers/net/wireless/mediatek/mt76/dma.h | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/net/wireless/mediatek/mt7

[Patch net 0/3] net_sched: some fixes for cls_tcindex

2019-02-10 Thread Cong Wang
This patchset contains 3 bug fixes for tcindex filter. Please check each patch for details. Signed-off-by: Cong Wang Cong Wang (3): net_sched: fix a race condition in tcindex_destroy() net_sched: fix a memory leak in cls_tcindex net_sched: fix two more memory leaks in cls_tcindex net/sch

[Patch net 3/3] net_sched: fix two more memory leaks in cls_tcindex

2019-02-10 Thread Cong Wang
struct tcindex_filter_result contains two parts: struct tcf_exts and struct tcf_result. For the local variable 'cr', its exts part is never used but initialized without being released properly on success path. So just completely remove the exts part to fix this leak. For the local variable 'new_f

[Patch net 2/3] net_sched: fix a memory leak in cls_tcindex

2019-02-10 Thread Cong Wang
When tcindex_destroy() destroys all the filter results in the perfect hash table, it invokes the walker to delete each of them. However, results with class==0 are skipped in either tcindex_walk() or tcindex_delete(), which causes a memory leak reported by kmemleak. This patch fixes it by skipping

[Patch net 1/3] net_sched: fix a race condition in tcindex_destroy()

2019-02-10 Thread Cong Wang
tcindex_destroy() invokes tcindex_destroy_element() via a walker to delete each filter result in its perfect hash table, and tcindex_destroy_element() calls tcindex_delete() which schedules tcf RCU works to do the final deletion work. Unfortunately this races with the RCU callback __tcindex_destroy

[PATCH net-next v3 1/9] Documentation: networking: switchdev: Update port parent ID section

2019-02-10 Thread Florian Fainelli
Update the section about switchdev drivers having to implement a switchdev_port_attr_get() function to return SWITCHDEV_ATTR_ID_PORT_PARENT_ID since that is no longer valid after commit bccb30254a4a ("net: Get rid of SWITCHDEV_ATTR_ID_PORT_PARENT_ID"). Fixes: bccb30254a4a ("net: Get rid of SWITCHD

[PATCH net-next v3 3/9] rocker: Handle SWITCHDEV_PORT_ATTR_GET/SET

2019-02-10 Thread Florian Fainelli
Following patches will change the way we communicate getting or setting a port's attribute and use a blocking notifier to perform those tasks. Prepare rocker to support receiving notifier events targeting SWITCHDEV_PORT_ATTR_GET/SET and simply translate that into the existing rocker_port_attr_{set

[PATCH net-next v3 0/9] net: Remove switchdev_ops

2019-02-10 Thread Florian Fainelli
Hi all, This patch series finishes by the removal of switchdev_ops. To get there we need to do a few things: - get rid of the one and only call to switchdev_port_attr_get() which is used to fetch the device's bridge port flags capabilities, instead we can just check what flags are being progr

[PATCH net-next v3 2/9] switchdev: Add SWITCHDEV_PORT_ATTR_SET, SWITCHDEV_PORT_ATTR_GET

2019-02-10 Thread Florian Fainelli
In preparation for allowing switchdev enabled drivers to veto specific attribute settings from within the context of the caller, introduce a new switchdev notifier type for port attributes. Suggested-by: Ido Schimmel Signed-off-by: Florian Fainelli --- include/net/switchdev.h | 10 ++ 1

[PATCH net-next v3 6/9] staging: fsl-dpaa2: ethsw: Handle SWITCHDEV_PORT_ATTR_GET/SET

2019-02-10 Thread Florian Fainelli
Following patches will change the way we communicate getting or setting a port's attribute and use a blocking notifier to perform those tasks. Prepare ethsw to support receiving notifier events targeting SWITCHDEV_PORT_ATTR_GET/SET and simply translate that into the existing swdev_port_attr_{set,g

[PATCH net-next v3 4/9] mlxsw: spectrum_switchdev: Handle SWITCHDEV_PORT_ATTR_GET/SET

2019-02-10 Thread Florian Fainelli
Following patches will change the way we communicate getting or setting a port's attribute and use a blocking notifier to perform those tasks. Prepare mlxsw to support receiving notifier events targeting SWITCHDEV_PORT_ATTR_GET/SET and simply translate that into the existing mlxsw_sp_port_attr_{se

[PATCH net-next v3 9/9] net: Remove switchdev_ops

2019-02-10 Thread Florian Fainelli
Now that we have converted all possible callers to using a switchdev notifier for attributes we do not have a need for implementing switchdev_ops anymore, and this can be removed from all drivers the net_device structure. Signed-off-by: Florian Fainelli --- drivers/net/ethernet/mellanox/mlxsw/sp

[PATCH net-next v3 7/9] net: dsa: Handle SWITCHDEV_PORT_ATTR_GET/SET

2019-02-10 Thread Florian Fainelli
Following patches will change the way we communicate getting or setting a port's attribute and use a blocking notifier to perform those tasks. Prepare DSA to support receiving notifier events targeting SWITCHDEV_PORT_ATTR_GET/SET and simply translate that into the existing dsa_slave_port_attr_{set

[PATCH net-next v3 5/9] net: mscc: ocelot: Handle SWITCHDEV_PORT_ATTR_GET/SET

2019-02-10 Thread Florian Fainelli
Following patches will change the way we communicate getting or setting a port's attribute and use a blocking notifier to perform those tasks. Prepare ocelot to support receiving notifier events targeting SWITCHDEV_PORT_ATTR_GET/SET and simply translate that into the existing ocelot_port_attr_{set

[PATCH net-next v3 8/9] net: switchdev: Replace port attr get/set SDO with a notification

2019-02-10 Thread Florian Fainelli
Drop switchdev_ops.switchdev_port_attr_get and _set. Drop the uses of this field from all clients, which were migrated to use switchdev notification in the previous patches. Add a new function switchdev_port_attr_notify() that sends the switchdev notifications SWITCHDEV_PORT_ATTR_GET and _SET. Up

Re: [PATCH net-next] ipmr: ip6mr: Create new sockopt to clear mfc cache or vifs

2019-02-10 Thread Nikolay Aleksandrov
On 2/11/19 12:12 AM, Callum Sinclair wrote: > Currently the only way to clear the forwarding cache was to delete the > entries one by one using the MRT_DEL_MFC socket option or to destroy and > recreate the socket. > > Create a new socket option which will clear the multicast forwarding > cache on

Re: [PATCH net-next v5 12/12] sock: Add SO_RCVTIMEO_NEW and SO_SNDTIMEO_NEW

2019-02-10 Thread Michael Ellerman
Deepa Dinamani writes: >> You touched powerpc in the previous patch but not this one. >> >> That's because we use the asm-generic version I assume. > > That is correct. > >> Would be good to mention in the change log though to avoid any confusion. > > I'm not sure how to do that now. It looks lik

[PATCH net-next] ipmr: ip6mr: Create new sockopt to clear mfc cache or vifs

2019-02-10 Thread Callum Sinclair
Created a way to clear the multicast forwarding cache on a socket without having to either remove the entries manually using the delete entry socket option or destroy and recreate the multicast socket. Using the flags MRT_FLUSH_ENTRIES and MRT_FLUSH_VIFS, all multicast entries can be cleared, all

[PATCH net-next] ipmr: ip6mr: Create new sockopt to clear mfc cache or vifs

2019-02-10 Thread Callum Sinclair
Currently the only way to clear the forwarding cache was to delete the entries one by one using the MRT_DEL_MFC socket option or to destroy and recreate the socket. Create a new socket option which will clear the multicast forwarding cache on the socket without destroying the socket. The new socke

Re: [PATCH v2 net 0/2] r8169: revert two commits due to a regression

2019-02-10 Thread David Miller
From: Heiner Kallweit Date: Sun, 10 Feb 2019 15:24:37 +0100 > Sander reported a regression (kernel panic, see[1]), therefore let's > revert these commits. Removal of the barriers doesn't seem to > contribute to the issue, the patch just overlaps with the problematic > one and only reverting both

Re: [PATCH net-next 0/3] net: phy: add and use register modifying helpers returning 1 on change

2019-02-10 Thread David Miller
From: Heiner Kallweit Date: Sun, 10 Feb 2019 19:56:47 +0100 > Add and use register modifying helpers returning 1 on change. Series applied, thanks.

[PATCH v2 bpf] bpf: fix lockdep false positive in stackmap

2019-02-10 Thread Alexei Starovoitov
Lockdep warns about false positive: [ 11.211460] [ cut here ] [ 11.211936] DEBUG_LOCKS_WARN_ON(depth <= 0) [ 11.211985] WARNING: CPU: 0 PID: 141 at ../kernel/locking/lockdep.c:3592 lock_release+0x1ad/0x280 [ 11.213134] Modules linked in: [ 11.214954] RIP: 0010:loc

Re: [PATCH net-next v2 00/16] net: Remove switchdev_ops

2019-02-10 Thread David Miller
From: Florian Fainelli Date: Sun, 10 Feb 2019 12:44:47 -0800 > I am going to submit a v3 which moves the port_attr_{get,set} to a > switchdev notifier, but does not yet get rid of > switchdev_port_attr_get() entirely since there is not a clear path yet > to split the setting between non-sleeping

Re: [PATCH net-next v2 00/16] net: Remove switchdev_ops

2019-02-10 Thread Florian Fainelli
Le 2/10/19 à 9:50 AM, Florian Fainelli a écrit : > Hi all, > > This patch series finishes by the removal of switchdev_ops. To get there > we need to do a few things: > > - get rid of the one and only call to switchdev_port_attr_get() which is > used to fetch the device's bridge port flags capab

Re: [PATCH for-next 4/4] devlink: add health command support

2019-02-10 Thread Stephen Hemminger
On Sun, 10 Feb 2019 20:28:49 +0200 Aya Levin wrote: > + > +static void cmd_health_help(void) > +{ > + pr_err("Usage: devlink health show [ dev DEV reporter REPORTER_NAME > ]\n"); > + pr_err("Usage: devlink health recover DEV reporter REPORTER_NAME\n"); > + pr_err("Usage: devlink heal

Re: [PATCH for-next 3/4] devlink: fix boolean JSON print

2019-02-10 Thread Stephen Hemminger
On Sun, 10 Feb 2019 20:28:48 +0200 Aya Levin wrote: > This patch removes the inverted commas from boolean values in JSON > format: true/false instead of "true"/"false". > > Signed-off-by: Aya Levin > Reviewed-by: Moshe Shemesh > --- > devlink/devlink.c | 6 +++--- > 1 file changed, 3 insertio

Re: [PATCH for-next 2/4] devlink: fix print of uint64_t

2019-02-10 Thread Stephen Hemminger
On Sun, 10 Feb 2019 20:28:47 +0200 Aya Levin wrote: > This patch prints uint64_t with its corresponding format and avoid implicit > cast to uint32_t. > > Signed-off-by: Aya Levin > Reviewed-by: Moshe Shemesh > Reported-by: Maria Pasechnik > --- > devlink/devlink.c | 9 - > 1 file c

Re: [PATCH net-next 3/3] net: phy: use phy_modify_changed in genphy_config_advert

2019-02-10 Thread Florian Fainelli
Le 2/10/19 à 10:59 AM, Heiner Kallweit a écrit : > Use phy_modify_changed() to simplify the code. > > Signed-off-by: Heiner Kallweit Reviewed-by: Florian Fainelli -- Florian

Re: [PATCH net-next 1/3] net: phy: add register modifying helpers returning 1 on change

2019-02-10 Thread Florian Fainelli
Le 2/10/19 à 10:57 AM, Heiner Kallweit a écrit : > When modifying registers there are scenarios where we need to know > whether the register content actually changed. This patch adds > new helpers to not break users of the current ones, phy_modify() etc. > > Signed-off-by: Heiner Kallweit Review

Re: [PATCH net-next 2/3] net: phy: marvell10g: fix usage of new MMD modifying helpers

2019-02-10 Thread Florian Fainelli
Le 2/10/19 à 10:58 AM, Heiner Kallweit a écrit : > When replacing mv3310_modify() with phy_modify_mmd() we missed that > they behave differently, mv3310_modify() returns 1 on a changed > register value whilst phy_modify_mmd() returns 0. Fix this by replacing > phy_modify_mmd() with phy_modify_mmd_c

Re: [PATCH net] sctp: make sctp_setsockopt_events() less strict about the option length

2019-02-10 Thread Marcelo Ricardo Leitner
On Sun, Feb 10, 2019 at 10:46:16AM -0200, Marcelo Ricardo Leitner wrote: > On Sat, Feb 09, 2019 at 03:12:17PM -0800, David Miller wrote: > > From: Marcelo Ricardo Leitner > > Date: Wed, 6 Feb 2019 18:37:54 -0200 > > > > > On Wed, Feb 06, 2019 at 12:14:30PM -0800, Julien Gomes wrote: > > >> Make s

linux-next: Fixes tag needs some work in the net tree

2019-02-10 Thread Stephen Rothwell
Hi all, In commit ccc8ca9b90ac ("net/smc: fix byte_order for rx_curs_confirmed") Fixes tag Fixes: b8649efad879 ("net/smc: fix sender_free computation") (net-tree) has these problem(s): - The trailing '(net-tree)' is unexpected -- Cheers, Stephen Rothwell pgpcW45lVtt8Q.pgp Descriptio

Re: [PATCH net-next 3/3] net: phy: use phy_modify_changed in genphy_config_advert

2019-02-10 Thread Andrew Lunn
On Sun, Feb 10, 2019 at 07:59:57PM +0100, Heiner Kallweit wrote: > Use phy_modify_changed() to simplify the code. > > Signed-off-by: Heiner Kallweit Reviewed-by: Andrew Lunn Andrew

Re: [PATCH net-next 2/3] net: phy: marvell10g: fix usage of new MMD modifying helpers

2019-02-10 Thread Andrew Lunn
On Sun, Feb 10, 2019 at 07:58:49PM +0100, Heiner Kallweit wrote: > When replacing mv3310_modify() with phy_modify_mmd() we missed that > they behave differently, mv3310_modify() returns 1 on a changed > register value whilst phy_modify_mmd() returns 0. Fix this by replacing > phy_modify_mmd() with

Re: [PATCH net-next 1/3] net: phy: add register modifying helpers returning 1 on change

2019-02-10 Thread Andrew Lunn
On Sun, Feb 10, 2019 at 07:57:56PM +0100, Heiner Kallweit wrote: > When modifying registers there are scenarios where we need to know > whether the register content actually changed. This patch adds > new helpers to not break users of the current ones, phy_modify() etc. > > Signed-off-by: Heiner K

Re: [PATCH net-next v2 06/16] net: bridge: Stop calling switchdev_port_attr_get()

2019-02-10 Thread Florian Fainelli
Le 2/10/19 à 11:05 AM, Ido Schimmel a écrit : > On Sun, Feb 10, 2019 at 09:50:55AM -0800, Florian Fainelli wrote: >> Now that all switchdev drivers have been converted to checking the >> bridge port flags during the prepare phase of the >> switchdev_port_attr_set(), we can move straight to trying t

Re: [PATCH net-next v2 06/16] net: bridge: Stop calling switchdev_port_attr_get()

2019-02-10 Thread Ido Schimmel
On Sun, Feb 10, 2019 at 09:50:55AM -0800, Florian Fainelli wrote: > Now that all switchdev drivers have been converted to checking the > bridge port flags during the prepare phase of the > switchdev_port_attr_set(), we can move straight to trying to set the > desired flag through SWITCHDEV_ATTR_ID_

[PATCH net-next 2/3] net: phy: marvell10g: fix usage of new MMD modifying helpers

2019-02-10 Thread Heiner Kallweit
When replacing mv3310_modify() with phy_modify_mmd() we missed that they behave differently, mv3310_modify() returns 1 on a changed register value whilst phy_modify_mmd() returns 0. Fix this by replacing phy_modify_mmd() with phy_modify_mmd_changed() where needed. Fixes: b52c018ddccf ("net: phy: m

[PATCH net-next 1/3] net: phy: add register modifying helpers returning 1 on change

2019-02-10 Thread Heiner Kallweit
When modifying registers there are scenarios where we need to know whether the register content actually changed. This patch adds new helpers to not break users of the current ones, phy_modify() etc. Signed-off-by: Heiner Kallweit --- drivers/net/phy/phy-core.c | 127

[PATCH net-next 3/3] net: phy: use phy_modify_changed in genphy_config_advert

2019-02-10 Thread Heiner Kallweit
Use phy_modify_changed() to simplify the code. Signed-off-by: Heiner Kallweit --- drivers/net/phy/phy_device.c | 43 +--- 1 file changed, 15 insertions(+), 28 deletions(-) diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c index 8573d17ec..3

[PATCH net-next 0/3] net: phy: add and use register modifying helpers returning 1 on change

2019-02-10 Thread Heiner Kallweit
Add and use register modifying helpers returning 1 on change. Heiner Kallweit (3): net: phy: add register modifying helpers returning 1 on change net: phy: marvell10g: fix usage of new MMD modifying helpers net: phy: use phy_modify_changed in genphy_config_advert drivers/net/phy/marvell10g

[iproute2-next, 0/4] Add support for devlink health

2019-02-10 Thread Aya Levin
This series adds support for devlink health commands: devlink health show [DEV reporter REPORTE_NAME] devlink health recoverDEV reporter REPORTER_NAME devlink health diagnose DEV reporter REPORTER_NAME devlink health dump show DEV reporter REPORTER_NAME devlink health dump clear

[PATCH for-next 4/4] devlink: add health command support

2019-02-10 Thread Aya Levin
This patch adds support for the following commands: devlink health show [DEV reporter REPORTE_NAME] devlink health recoverDEV reporter REPORTER_NAME devlink health diagnose DEV reporter REPORTER_NAME devlink health dump show DEV reporter REPORTER_NAME devlink health dump clear DEV repor

Re: tc qdisc kernel crash

2019-02-10 Thread Cong Wang
On Sun, Feb 10, 2019 at 7:54 AM Ben Hutchings wrote: > > Control: tag -1 confirmed upstream > Control: found -1 4.20-1~exp1 > > Adrian (cc'd) reported (https://bugs.debian.org/921542) that a script > using tc could trigger a kernel crash. I've simplified the script he > provided down to: > > ---

[PATCH for-next 3/4] devlink: fix boolean JSON print

2019-02-10 Thread Aya Levin
This patch removes the inverted commas from boolean values in JSON format: true/false instead of "true"/"false". Signed-off-by: Aya Levin Reviewed-by: Moshe Shemesh --- devlink/devlink.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/devlink/devlink.c b/devlink/devlin

[PATCH for-next 2/4] devlink: fix print of uint64_t

2019-02-10 Thread Aya Levin
This patch prints uint64_t with its corresponding format and avoid implicit cast to uint32_t. Signed-off-by: Aya Levin Reviewed-by: Moshe Shemesh Reported-by: Maria Pasechnik --- devlink/devlink.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/devlink/devlink.c b

[iproute2-next, 0/4] Add support for devlink health

2019-02-10 Thread Aya Levin
This series adds support for devlink health commands: devlink health show [DEV reporter REPORTE_NAME] devlink health recoverDEV reporter REPORTER_NAME devlink health diagnose DEV reporter REPORTER_NAME devlink health dump show DEV reporter REPORTER_NAME devlink health dump clear

[PATCH for-next 1/4] devlink: refactor validation of finding required arguments

2019-02-10 Thread Aya Levin
Introducing argument's metadata structure matching a bitmap flag per required argument and an error message if missing. Using this static array to refactor validation of finding required arguments in devlink command line and to ease further maintenance. Signed-off-by: Aya Levin Reviewed-by: Moshe

[PATCH net-next v2 05/16] rocker: Check bridge flags during prepare phase

2019-02-10 Thread Florian Fainelli
In preparation for getting rid of switchdev_port_attr_get(), have rocker check for the bridge flags being set through switchdev_port_attr_set() with the SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS attribute identifier. Acked-by: Jiri Pirko Signed-off-by: Florian Fainelli --- drivers/net/ethernet/rocker

[PATCH net-next v2 07/16] net: Remove SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS_SUPPORT

2019-02-10 Thread Florian Fainelli
Now that we have converted the bridge code and the drivers to check for bridge port(s) flags at the time we try to set them, there is no need for a get() -> set() sequence anymore and SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS_SUPPORT therefore becomes unused. Acked-by: Jiri Pirko Signed-off-by: Florian

[PATCH net-next v2 14/16] staging: fsl-dpaa2: ethsw: Handle SWITCHDEV_PORT_ATTR_SET

2019-02-10 Thread Florian Fainelli
Following patches will change the way we communicate getting or setting a port's attribute and use a blocking notifier to perform those tasks. Prepare ethsw to support receiving notifier events targeting SWITCHDEV_PORT_ATTR_SET and simply translate that into the existing swdev_port_attr_set() call

[PATCH net-next v2 12/16] mlxsw: spectrum_switchdev: Handle SWITCHDEV_PORT_ATTR_SET

2019-02-10 Thread Florian Fainelli
Following patches will change the way we communicate getting or setting a port's attribute and use a blocking notifier to perform those tasks. Prepare mlxsw to support receiving notifier events targeting SWITCHDEV_PORT_ATTR_SET and simply translate that into the existing mlxsw_sp_port_attr_set() c

[PATCH net-next v2 00/16] net: Remove switchdev_ops

2019-02-10 Thread Florian Fainelli
Hi all, This patch series finishes by the removal of switchdev_ops. To get there we need to do a few things: - get rid of the one and only call to switchdev_port_attr_get() which is used to fetch the device's bridge port flags capabilities, instead we can just check what flags are being progr

[PATCH net-next v2 03/16] staging: fsl-dpaa2: ethsw: Check bridge port flags during set

2019-02-10 Thread Florian Fainelli
In preparation for removing SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS_SUPPORT, have ethsw check that the bridge port flags that are being set are supported. Acked-by: Jiri Pirko Signed-off-by: Florian Fainelli --- drivers/staging/fsl-dpaa2/ethsw/ethsw.c | 5 - 1 file changed, 4 insertions(+), 1 d

[PATCH net-next v2 02/16] mlxsw: spectrum: Check bridge flags during prepare phase

2019-02-10 Thread Florian Fainelli
In preparation for getting rid of switchdev_port_attr_get(), have mlxsw check for the bridge flags being set through switchdev_port_attr_set() with the SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS attribute identifier. Acked-by: Jiri Pirko Signed-off-by: Florian Fainelli --- drivers/net/ethernet/mellano

[PATCH net-next v2 06/16] net: bridge: Stop calling switchdev_port_attr_get()

2019-02-10 Thread Florian Fainelli
Now that all switchdev drivers have been converted to checking the bridge port flags during the prepare phase of the switchdev_port_attr_set(), we can move straight to trying to set the desired flag through SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS. Acked-by: Jiri Pirko Signed-off-by: Florian Fainelli

[PATCH net-next v2 04/16] net: dsa: Add setter for SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS

2019-02-10 Thread Florian Fainelli
In preparation for removing SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS_SUPPORT, add support for a function that processes the SWITCHDEV_ATTR_ID_PORT_BRIDGE_FLAGS attribute and returns not supported for any flag set, since DSA does not currently support toggling those bridge port attributes (yet). Acked-b

[PATCH net-next v2 01/16] Documentation: networking: switchdev: Update port parent ID section

2019-02-10 Thread Florian Fainelli
Update the section about switchdev drivers having to implement a switchdev_port_attr_get() function to return SWITCHDEV_ATTR_ID_PORT_PARENT_ID since that is no longer valid after commit bccb30254a4a ("net: Get rid of SWITCHDEV_ATTR_ID_PORT_PARENT_ID"). Fixes: bccb30254a4a ("net: Get rid of SWITCHD

[PATCH net-next v2 08/16] net: Get rid of switchdev_port_attr_get()

2019-02-10 Thread Florian Fainelli
With the bridge no longer calling switchdev_port_attr_get() to obtain the supported bridge port flags from a driver but instead trying to set the bridge port flags directly and relying on driver to reject unsupported configurations, we can effectively get rid of switchdev_port_attr_get() entirely s

  1   2   >