[PATCH v7 2/3] Bluetooth: btusb: Add out-of-band wakeup support

Some onboard BT chips (e.g. Marvell 8997) contain a wakeup pin that can be connected to a gpio on the CPU side, and can be used to wakeup the host out-of-band. This can be useful in situations where the in-band wakeup is not possible or not preferable (e.g. the in-band wakeup may require the USB

[PATCH v7 3/3] Bluetooth: btusb: Configure Marvell to use one of the pins for oob wakeup

The Marvell devices may have many gpio pins, and hence for wakeup on these out-of-band pins, the chip needs to be told which pin is to be used for wakeup, using an hci command. Thus, we read the pin number etc from the device tree node and send a command to the chip. Signed-off-by: Rajat Jain

Re: net: suspicious RCU usage in nf_hook

On Wed, Feb 1, 2017 at 1:16 PM, Eric Dumazet wrote: > On Wed, 2017-02-01 at 12:51 -0800, Cong Wang wrote: >> On Tue, Jan 31, 2017 at 7:44 AM, Eric Dumazet wrote: >> > On Mon, 2017-01-30 at 22:19 -0800, Cong Wang wrote: >> > >> >> >> >> The context

Re: [PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()

On 01/31/2017 12:47 PM, Boris Ostrovsky wrote: > On 01/30/2017 02:31 PM, Boris Ostrovsky wrote: >> On 01/30/2017 02:06 PM, Eric Dumazet wrote: >>> On Mon, 2017-01-30 at 13:23 -0500, Boris Ostrovsky wrote: >>> We do netif_carrier_off() first thing in xennet_disconnect_backend() and the

[PATCH net-next] net: phy: marvell: Add support for 88e1545 PHY

The 88e1545 PHYs are discrete Marvell PHYs, found in a quad package on the zii-devel-b board. Add support for it to the Marvell PHY driver. Signed-off-by: Andrew Lunn --- NOTE: To apply cleanly, the "Work around missing PHY product ID in mv88e6390" patches need to be applied

[PATCHv2 net-next 0/2] MV88E6390 fixes

Two patches, which have been posted before. Fix simple issues in the mv88e6390 support. These don't need to go to stable, since the mv88e6390 support in stable is insufficient to be usable. To apply cleanly, these patches rely on "net: dsa: mv88e6xxx: Workaround missing PHY". v2: Added

Re: [net-next 1/8] net/mlx5: Fixed static checker warnings

On Wed, Feb 1, 2017 at 7:22 PM, David Miller wrote: [..] > You're propagating values into a u32 field, which you are explicitly > performing 32-bit endianness conversions upon. > Just use "u32" for a local variable and get rid of all of these casts. ok, will do that

[PATCH iproute2] ss: print tcpi_rcv_mss

From: Eric Dumazet tcpi_rcv_mss tcp info field was not yet reported by ss. While adding GRO support to packetdrill, I found this was useful. Signed-off-by: Eric Dumazet --- misc/ss.c |4 1 file changed, 4 insertions(+) diff --git

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

Hi Andrew, > > We would need a tri-state device tree properly: > > > > 1. Not defined - do nothing > > 2. Defined as 0 -> explicitly disable port mirroring > > 3. Defined as 1 -> explicitly enable port mirriring > > > > The "net-phy-lane-swap" only fulfills points 1 and 3 above. > > > > In my

Re: [PATCHv3 net-next 5/7] net: add confirm_neigh method to dst_ops

Hello, On Wed, 1 Feb 2017, Steffen Klassert wrote: > On Tue, Jan 31, 2017 at 11:57:05PM +0200, Julian Anastasov wrote: > > > > +static void xfrm_confirm_neigh(const struct dst_entry *dst, const void > > *daddr) > > +{ > > + const struct dst_entry *path = dst->path; > > + > > + if

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

> We would need a tri-state device tree properly: > > 1. Not defined - do nothing > 2. Defined as 0 -> explicitly disable port mirroring > 3. Defined as 1 -> explicitly enable port mirriring > > The "net-phy-lane-swap" only fulfills points 1 and 3 above. > > In my use case I do need point 2.

[PATCH] wcn36xx: Implement cancel_hw_scan

In the even that the wcn36xx interface is brought down while a hw_scan is active we must abort and wait for the ongoing scan to signal completion to mac80211. Reported-by: Mart Raudsepp Fixes: 886039036c20 ("wcn36xx: Implement firmware assisted scan") Signed-off-by: Bjorn

Re: net: suspicious RCU usage in nf_hook

On Wed, 2017-02-01 at 15:48 -0800, Eric Dumazet wrote: > On Wed, Feb 1, 2017 at 3:29 PM, Cong Wang wrote: > > > Not sure if it is better. The difference is caught up in > > net_enable_timestamp(), > > which is called setsockopt() path and sk_clone() path, so we could

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

On 02/01/2017 01:05 PM, Lukasz Majewski wrote: > Dear All, > > Thanks for prompt reply. > >> On 02/01/2017 09:16 AM, Andrew Lunn wrote: >>> On Wed, Feb 01, 2017 at 03:43:35PM +0100, Lukasz Majewski wrote: This patch adds support for enabling or disabling the port mirroring feature of

Re: net: suspicious RCU usage in nf_hook

On Wed, 2017-02-01 at 13:16 -0800, Eric Dumazet wrote: > This would permanently leave the kernel in the netstamp_needed state. > > I would prefer the patch using a process context to perform the > cleanup ? Note there is a race window, but probably not a big deal. > > net/core/dev.c | 30

Re: net: suspicious RCU usage in nf_hook

On Wed, Feb 1, 2017 at 3:29 PM, Cong Wang wrote: > Not sure if it is better. The difference is caught up in > net_enable_timestamp(), > which is called setsockopt() path and sk_clone() path, so we could be > in netstamp_needed state for a long time too until user-space

Re: [PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()

On Wed, 2017-02-01 at 18:29 -0500, Boris Ostrovsky wrote: > > I could not convince myself that napi_synchronize() is sufficient here > (mostly because I am not familiar with napi flow). At the same time I > would rather not make changes in anticipation of possible disappearance > of

Re: [PATCH 1/2] net: ethernet: bgmac: init sequence bug

How about BCMA_IOCTL_PRESERVE_ACROSS_INIT? On Wed, Feb 1, 2017 at 6:06 PM, Rafał Miłecki wrote: > On 02/01/2017 11:39 PM, Jon Mason wrote: >> >> From: Zac Schroff >> >> Fix a bug in the 'bgmac' driver init sequence that blind writes for init >> sequence

Re: [PATCH v2 2/4] net: phy: Initialize mdio clock at probe function

On 01/17/2017 08:14 AM, Yendapally Reddy Dhananjaya Reddy wrote: > Initialize mdio clock divisor in probe function. The ext bus > bit available in the same register will be used by mdio mux > to enable external mdio. > > Signed-off-by: Yendapally Reddy Dhananjaya Reddy >

[PATCH 1/2] net: ethernet: bgmac: init sequence bug

From: Zac Schroff Fix a bug in the 'bgmac' driver init sequence that blind writes for init sequence where it should preserve most bits other than the ones it is deliberately manipulating. Signed-off-by: Zac Schroff Signed-off-by: Jon Mason

[PATCH 2/2] net: ethernet: bgmac: mac address change bug

From: Hari Vyas ndo_set_mac_address() passes struct sockaddr * as 2nd parameter to bgmac_set_mac_address() but code assumed u8 *. This caused two bytes chopping and the wrong mac address was configured. Signed-off-by: Hari Vyas Signed-off-by: Jon Mason

[PATCH 0/2] net: ethernet: bgmac: bug fixes

Bug fixes for bgmac driver Hari Vyas (1): net: ethernet: bgmac: mac address change bug Zac Schroff (1): net: ethernet: bgmac: init sequence bug drivers/net/ethernet/broadcom/bgmac-platform.c | 10 +++--- drivers/net/ethernet/broadcom/bgmac.c | 6 +-

[PATCH v7 1/3] Bluetooth: btusb: Use an error label for error paths

Use a label to remove the repetetive cleanup, for error cases. Signed-off-by: Rajat Jain Reviewed-by: Brian Norris --- v7: same as v6 v6: same as v5 v5: same as v4 v4: same as v3 v3: Added Brian's "Reviewed-by" v2: same as v1

Re: [PATCH 1/2] net: ethernet: bgmac: init sequence bug

On 02/01/2017 11:39 PM, Jon Mason wrote: From: Zac Schroff Fix a bug in the 'bgmac' driver init sequence that blind writes for init sequence where it should preserve most bits other than the ones it is deliberately manipulating. Signed-off-by: Zac Schroff

Re: [PATCH net-next] loopback: clear pfmemalloc on outgoing skb's

On Wed, 2017-02-01 at 16:04 -0500, Josef Bacik wrote: > I was seeing random disconnects while testing NBD over loopback. This turned > out to be because NBD sets pfmemalloc on it's socket, however the receiving > side > is a user space application so does not have pfmemalloc set on its socket.

[PATCHv2 net-next 1/2] net: dsa: mv88e6xxx: Fix ATU age timer for MV88E6390

The MV88E6390 family uses a different ATU age timer coefficient. Fix the info structures. Signed-off-by: Andrew Lunn Reviewed-by: Vivien Didelot --- v2: Remove redundant "the". Add Reviewed-by --- drivers/net/dsa/mv88e6xxx/chip.c | 12

[PATCHv2 net-next 2/2] net: dsa: mv88e6xxx: Fix typ0 when configuring 2.5Gbps

In order to enable 2.5Gbps mode, we need the base speed of 10G, plus the Alt bit setting. Fix a typ0 that used 1Gb base speed. Signed-off-by: Andrew Lunn Reviewed-by: Vivien Didelot --- v2: Add Reviewed-by ---

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

> What a poorly chosen name though... in Ethernet world, port mirroring > means the ability to capture traffic from a vector of ports and copying > it verbatim (or sampled) towards a capture port, aka the mirror port... Ack. We should avoid "port mirroring" in what ever patch we decide upon.

Re: net: suspicious RCU usage in nf_hook

On Wed, 2017-02-01 at 12:51 -0800, Cong Wang wrote: > On Tue, Jan 31, 2017 at 7:44 AM, Eric Dumazet wrote: > > On Mon, 2017-01-30 at 22:19 -0800, Cong Wang wrote: > > > >> > >> The context is process context (TX path before hitting qdisc), and > >> BH is not disabled, so

Re: [PATCH net-next] loopback: clear pfmemalloc on outgoing skb's

On Wed, 2017-02-01 at 15:38 -0800, Eric Dumazet wrote: > On Wed, 2017-02-01 at 16:04 -0500, Josef Bacik wrote: > > I was seeing random disconnects while testing NBD over loopback. This > > turned > > out to be because NBD sets pfmemalloc on it's socket, however the receiving > > side > > is a

[PATCH v2] net: stmmac: Fix wrong message in stmmac_probe_config_dt

Most likely a copy & paste error in referenced commit. Restore the debug message to what it was before. Fixes: f573c0b9c4e0 ("stmmac: move stmmac_clk, pclk, clk_ptp_ref and stmmac_rst to platform structure") Signed-off-by: Heiner Kallweit --- v2: - Don't remove the wrong

Re: [PATCH] net: stmmac: Remove wrong message in stmmac_probe_config_dt

On 2/02/2017 05:05, Heiner Kallweit wrote: I can only imagine that this message ended up there by a copy & paste mistake. The same message appears correctly a few lines later, but here it doesn't make sense. Signed-off-by: Heiner Kallweit ---

Re: [PATCH net] net: phy: Fix lack of reference count on PHY driver

On 02/01/2017 11:10 AM, Russell King - ARM Linux wrote: > On Wed, Feb 01, 2017 at 01:59:38PM -0500, David Miller wrote: >> From: Florian Fainelli >> Date: Wed, 1 Feb 2017 10:55:46 -0800 >> >>> You are right, but there is still a fundamental problem IMHO in that you >>>

[PATCH net-next] cxgb4: Fix uld_send() for ctrl pkts

From: Arjun V Without any uld being loaded, uld_txq_info[] will be NULL. uld_send() is also used for sending control work requests(for eg: setting filter) that dont require any ulds to be loaded. Hence move uld_txq_info[] assignment after ctrl_xmit(). Also added a NULL check

Re: [PATCH] net: phy: dp83867: Port mirroring support in the DP83867 TI's PHY driver

On Wed, Feb 01, 2017 at 11:13:23PM +0100, Lukasz Majewski wrote: > Hi Andrew, > > > > We would need a tri-state device tree properly: > > > > > > 1. Not defined - do nothing > > > 2. Defined as 0 -> explicitly disable port mirroring > > > 3. Defined as 1 -> explicitly enable port mirriring > > >

Re: [PATCH net-next] net: phy: marvell: Add support for 88e1545 PHY

On 02/01/2017 03:35 PM, Andrew Lunn wrote: > The 88e1545 PHYs are discrete Marvell PHYs, found in a quad package on > the zii-devel-b board. Add support for it to the Marvell PHY driver. > > Signed-off-by: Andrew Lunn Reviewed-by: Florian Fainelli --

[PATCH net-next] net: ipv4: remove fib_lookup.h from devinet.c include list

nothing in devinet.c relies on fib_lookup.h; remove it from the includes Signed-off-by: David Ahern --- net/ipv4/devinet.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/net/ipv4/devinet.c b/net/ipv4/devinet.c index 4cd2ee8857d2..5d367b7ff542 100644 ---

Re: [PATCH net] net: phy: Fix lack of reference count on PHY driver

On 02/01/2017 02:51 AM, Russell King - ARM Linux wrote: > It looks to me as if that's the only case where this can happen, so maybe > the above needs to be: > > if (phydev->drv && phydev->drv->link_change_notify) > phydev->drv->link_change_notify(phydev); > > Also, I'd

Re: [PATCH 1/2] Documentation: devicetree: change the mediatek ethernet compatible string

On Wed, 2017-01-25 at 09:20 +0100, John Crispin wrote: > When the binding was defined, I was not aware that mt2701 was an earlier > version of the SoC. For sake of consistency, the ethernet driver should > use mt2701 inside the compat string as this is the earliest SoC with the > ethernet core. >

Re: [PATCH 2/2] net-next: ethernet: mediatek: change the compatible string

On Wed, 2017-01-25 at 09:20 +0100, John Crispin wrote: > When the binding was defined, I was not aware that mt2701 was an earlier > version of the SoC. For sake of consistency, the ethernet driver should > use mt2701 inside the compat string as this is the earliest SoC with the > ethernet core. >

Re: [PATCH net-next v2 0/5] bridge: per vlan dst_metadata support

On 2/1/17, 8:04 PM, Stephen Hemminger wrote: > On Wed, 01 Feb 2017 20:02:35 -0800 > Roopa Prabhu wrote: > >> On 2/1/17, 5:59 PM, David Ahern wrote: >>> On 2/1/17 6:23 PM, Alexei Starovoitov wrote: On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote:

Re: [PATCH net-next v2 0/5] bridge: per vlan dst_metadata support

On Wed, 01 Feb 2017 21:58:25 -0800 Roopa Prabhu wrote: > On 2/1/17, 5:23 PM, Alexei Starovoitov wrote: > > On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote: > > > > [snip] > > >> Solution in this patch series: > >> The Goal is to use a single vxlan

Re: [net-next ovs clone action 3/3] openvswitch: kernel datapath clone action

On Tue, Jan 31, 2017 at 8:47 AM, Andy Zhou wrote: > Add 'clone' kernel datapath support. In case the actions within clone > do not modify the current flow, the actions are executed without > making a copy of current key before execution. This analysis is > done once per flow

[PATCH net-next] net: add LINUX_MIB_PFMEMALLOCDROP counter

From: Eric Dumazet Debugging issues caused by pfmemalloc is often tedious. Add a new SNMP counter to more easily diagnose these problems. Signed-off-by: Eric Dumazet Cc: Josef Bacik --- include/uapi/linux/snmp.h |1 +

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

Hi all, Today's linux-next merge of the net-next tree got a conflict in: net/sched/cls_matchall.c between commit: fd62d9f5c575 ("net/sched: matchall: Fix configuration race") from Linus' tree and commit: ec2507d2a306 ("net/sched: cls_matchall: Fix error path") from the net-next tree.

Re: [PATCH net-next v2 0/5] bridge: per vlan dst_metadata support

On 2/1/17 6:23 PM, Alexei Starovoitov wrote: > On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote: >> >> This provides the required vxlan bridging function but poses a >> scalability problem with using a separate vxlan netdev for each vni. > if I remember correctly

Re: [net-next ovs clone action 3/3] openvswitch: kernel datapath clone action

On Wed, Feb 1, 2017 at 6:30 PM, Pravin Shelar wrote: > On Tue, Jan 31, 2017 at 8:47 AM, Andy Zhou wrote: >> Add 'clone' kernel datapath support. In case the actions within clone >> do not modify the current flow, the actions are executed without >> making a copy

Re: [PATCH net-next v2 0/5] bridge: per vlan dst_metadata support

On 2/1/17, 5:59 PM, David Ahern wrote: > On 2/1/17 6:23 PM, Alexei Starovoitov wrote: >> On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote: >>> >>> This provides the required vxlan bridging function but poses a >>> scalability problem with using a separate vxlan

Re: [PATCH] net: stmmac: Remove wrong message in stmmac_probe_config_dt

Am 02.02.2017 um 03:20 schrieb Phil Reid: > On 2/02/2017 05:05, Heiner Kallweit wrote: >> I can only imagine that this message ended up there by a copy & paste >> mistake. The same message appears correctly a few lines later, but >> here it doesn't make sense. >> >> Signed-off-by: Heiner Kallweit

Re: [PATCH net-next v2 0/5] bridge: per vlan dst_metadata support

On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote: > > This provides the required vxlan bridging function but poses a > scalability problem with using a separate vxlan netdev for each vni. if I remember correctly this issue was the main reason David Ahern put

[PATCH net-next] net: remove useless pfmemalloc setting

From: Eric Dumazet When __alloc_skb() allocates an skb from fast clone cache, setting pfmemalloc on the clone is not needed. Clone will be properly initialized later at skb_clone() time, including pfmemalloc field, as it is included in the headers_start/headers_end section

Re: [PATCH net-next v2 0/5] bridge: per vlan dst_metadata support

On Wed, 01 Feb 2017 20:02:35 -0800 Roopa Prabhu wrote: > On 2/1/17, 5:59 PM, David Ahern wrote: > > On 2/1/17 6:23 PM, Alexei Starovoitov wrote: > >> On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote: > >>> > >>> This provides the

Re: [PATCH net-next v2 0/5] bridge: per vlan dst_metadata support

On 2/1/17, 5:23 PM, Alexei Starovoitov wrote: > On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote: > [snip] >> Solution in this patch series: >> The Goal is to use a single vxlan device to carry all vnis similar >> to the vxlan collect metadata mode but additionally allowing the

Re: [PATCH net-next] loopback: clear pfmemalloc on outgoing skb's

On Wed, 2017-02-01 at 15:38 -0800, Eric Dumazet wrote: > I am not sure this is a proper fix. > > Presumably if the socket was able to store packets in its write queue, > fact that it sends it to loopback or an Ethernet link should not matter. > > Only in RX path the pfmemalloc thing is really

Re: [PATCH v2 3/4] phy: Add USB3 PHY support for Broadcom NSP SoC

[Resending with fixed/complete Cc-s] On Tue, 17 Jan 2017 11:14:29 -0500, Yendapally Reddy Dhananjaya Reddy wrote:> This patch adds support for Broadcom NSP USB3 PHY > > Signed-off-by: Yendapally Reddy Dhananjaya Reddy

[patch net-next] sfc: a couple off by one bugs

These checks are off by one. These are just sanity checks and we don't ever pass invalid values for "encap_type" so it's harmless. Fixes: 9b4108012517 ("sfc: insert catch-all filters for encapsulated traffic") Signed-off-by: Dan Carpenter diff --git

Re: [PATCH net] net: phy: Fix lack of reference count on PHY driver

On Tue, Jan 31, 2017 at 06:46:43PM -0800, Florian Fainelli wrote: > From: Mao Wenan > > There is currently no reference count being held on the PHY driver, > which makes it possible to remove the PHY driver module while the PHY > state machine is running and polling the PHY.

Re: [PATCH V2 2/2] qedf: Add QLogic FastLinQ offload FCoE driver framework.

On 01/31/2017 06:08 PM, Chad Dupuis wrote: On Mon, 30 Jan 2017, 10:34am -, Hannes Reinecke wrote: On 01/25/2017 09:33 PM, Dupuis, Chad wrote: From: "Dupuis, Chad" [ .. ] + if (opcode == ELS_LS_RJT) { + rjt = fc_frame_payload_get(fp,

Re: [PATCH net-next 1/3] trace: add variant without spacing in trace_print_hex_seq

On 01/30/2017 09:44 PM, Steven Rostedt wrote: On Wed, 25 Jan 2017 02:28:16 +0100 Daniel Borkmann wrote: For upcoming tracepoint support for BPF, we want to dump the program's tag. Format should be similar to __print_hex(), but without spacing. Add a __print_hex_str()

Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data

On Tuesday 31 January 2017 07:59:18 Tony Lindgren wrote: > * Kalle Valo [170130 22:36]: > > Tony Lindgren writes: > > > > > * Pavel Machek [170127 11:41]: > > >> On Fri 2017-01-27 17:23:07, Kalle Valo wrote: > > >> > Pali Rohár

pull-request: wireless-drivers-next 2017-02-01

Hi Dave, here's a pull request to 4.11, more details in the signed tag below. I forgot to mention in the tag that this includes one small change to include/linux/soc/qcom/smem_state.h which was acked by Andy Gross in commit 6c0b2e833f14. It was needed to fix a build problem with wcn36xx using

Re: [PATCH 4.10-rc3 03/13] net: macb: fix build errors when linux/phy*.h is removed from net/dsa.h

Le 31/01/2017 à 20:18, Russell King a écrit : > drivers/net/ethernet/cadence/macb.h:862:33: sparse: expected ; at end of > declaration > drivers/net/ethernet/cadence/macb.h:862:33: sparse: Expected } at end of > struct-union-enum-specifier > drivers/net/ethernet/cadence/macb.h:862:33: sparse:

Re: [PATCH net-next] net: phy: Add LED mode driver for Microsemi PHYs.

Hi Andrew, Thank you for review and valuable comments. On Tue, Jan 31, 2017 at 02:30:09PM +0100, Andrew Lunn wrote: > EXTERNAL EMAIL > > > On Tue, Jan 31, 2017 at 11:16:01AM +0530, Raju Lakkaraju wrote: > > From: Raju Lakkaraju > > > > LED Mode: > > Microsemi PHY

Re: [PATCH 4.10-rc3 07/13] net: mvneta: fix build errors when linux/phy*.h is removed from net/dsa.h

Hello, On Tue, 31 Jan 2017 19:18:59 +, Russell King wrote: > drivers/net/ethernet/marvell/mvneta.c:2694:26: error: storage size of > 'status' isn't known > drivers/net/ethernet/marvell/mvneta.c:2695:26: error: storage size of > 'changed' isn't known >

routing policy based on u32 classifier

Hello everyone, Kindly I would like to ask if there is a way to do routing policy based on u32 classifier without fwmark/netfilter. I have read doc/tc-filters and doc/actions/actions-general from iproute2-4.9.0 package but I am not able to find any actions doing this kind of job: the only way is

pull request (net-next): ipsec-next 2017-02-01

1) Some typo fixes, from Alexander Alemayhu. 2) Don't acquire state lock in get_mtu functions. The only rece against a dead state does not matter. From Florian Westphal. 3) Remove xfrm4_state_fini, it is unused for more than 10 years. From Florian Westphal. 4) Various rcu usage

[PATCH 04/15] xfrm: avoid rcu sparse warning

From: Florian Westphal xfrm/xfrm_state.c:1973:21: error: incompatible types in comparison expression (different address spaces) Harmless, but lets fix it to reduce the noise. While at it, get rid of unneeded NULL check, its never hit: net/ipv4/xfrm4_state.c:

[PATCH 11/15] esp4: Avoid skb_cow_data whenever possible

This patch tries to avoid skb_cow_data on esp4. On the encrypt side we add the IPsec tailbits to the linear part of the buffer if there is space on it. If there is no space on the linear part, we add a page fragment with the tailbits to the buffer and use separate src and dst scatterlists. On

[PATCH 06/15] xfrm: add and use xfrm_state_afinfo_get_rcu

From: Florian Westphal xfrm_init_tempstate is always called from within rcu read side section. We can thus use a simpler function that doesn't call rcu_read_lock again. While at it, also make xfrm_init_tempstate return value void, the return value was never tested. A followup

[PATCH 01/15] xfrm: trivial typos

From: Alexander Alemayhu o s/descentant/descendant o s/workarbound/workaround Signed-off-by: Alexander Alemayhu Signed-off-by: Steffen Klassert --- net/xfrm/xfrm_policy.c | 2 +- net/xfrm/xfrm_state.c | 2 +- 2

[PATCH 05/15] xfrm: remove xfrm_state_put_afinfo

From: Florian Westphal commit 44abdc3047aecafc141dfbaf1ed ("xfrm: replace rwlock on xfrm_state_afinfo with rcu") made xfrm_state_put_afinfo equivalent to rcu_read_unlock. Use spatch to replace it with direct calls to rcu_read_unlock: @@ struct xfrm_state_afinfo *a; @@ -

[PATCH 12/15] esp6: Avoid skb_cow_data whenever possible

This patch tries to avoid skb_cow_data on esp6. On the encrypt side we add the IPsec tailbits to the linear part of the buffer if there is space on it. If there is no space on the linear part, we add a page fragment with the tailbits to the buffer and use separate src and dst scatterlists. On

[PATCH 09/15] IPsec: do not ignore crypto err in ah4 input

From: Gilad Ben-Yossef ah4 input processing uses the asynchronous hash crypto API which supplies an error code as part of the operation completion but the error code was being ignored. Treat a crypto API error indication as a verification failure. While a crypto API

[PATCH 07/15] xfrm: state: simplify rcu_read_unlock handling in two spots

From: Florian Westphal Instead of: if (foo) { unlock(); return bar(); } unlock(); do: unlock(); if (foo) return bar(); This is ok because rcu protected structure is only dereferenced before the conditional. Signed-off-by: Florian Westphal

[PATCH 08/15] xfrm: fix possible null deref in xfrm_init_tempstate

From: Florian Westphal Dan reports following smatch warning: net/xfrm/xfrm_state.c:659 error: we previously assumed 'afinfo' could be null (see line 651) 649 struct xfrm_state_afinfo *afinfo = xfrm_state_afinfo_get_rcu(family); 651 if (afinfo) ... 658 }

[PATCH 10/15] IPsec: do not ignore crypto err in ah6 input

From: Gilad Ben-Yossef ah6 input processing uses the asynchronous hash crypto API which supplies an error code as part of the operation completion but the error code was being ignored. Treat a crypto API error indication as a verification failure. While a crypto API

[PATCH 02/15] xfrm: state: do not acquire lock in get_mtu helpers

From: Florian Westphal Once flow cache gets removed the mtu initialisation happens for every skb that gets an xfrm attached, so this lock starts to show up in perf. It is not obvious why this lock is required -- the caller holds reference on the state struct, type->destructor is

[PATCH 14/15] net: Drop secpath on free after gro merge.

With a followup patch, a gro merged skb can have a secpath. So drop it before freeing or reusing the skb. Signed-off-by: Steffen Klassert --- net/core/dev.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/net/core/dev.c b/net/core/dev.c index 56818f7..ef3a969

[PATCH 13/15] esp: Introduce a helper to setup the trailer

We need to setup the trailer in two different cases, so add a helper to avoid code duplication. Signed-off-by: Steffen Klassert --- net/ipv4/esp4.c | 44 +++- net/ipv6/esp6.c | 44 +++-

[PATCH 03/15] xfrm: remove unused function

From: Florian Westphal Has been ifdef'd out for more than 10 years, remove it. Signed-off-by: Florian Westphal Signed-off-by: Steffen Klassert --- net/ipv4/xfrm4_state.c | 8 1 file changed, 8 deletions(-) diff --git

[PATCH 15/15] xfrm: Add a dummy network device for napi.

This patch adds a dummy network device so that we can use gro_cells for IPsec GRO. With this, we handle IPsec GRO with no impact on the generic networking code. Signed-off-by: Steffen Klassert --- net/xfrm/xfrm_input.c | 12 +++- 1 file changed, 11

[patch net-next] ethernet: aquantia: fix dma_mapping_error test

dma_mapping_error() returns 1 if there is an error and 0 if not. Fixes: 018423e90bee ("net: ethernet: aquantia: Add ring support code") Signed-off-by: Dan Carpenter diff --git a/drivers/net/ethernet/aquantia/atlantic/aq_ring.c

Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data

On 1 February 2017 at 09:33, Pali Rohár wrote: > On Tuesday 31 January 2017 07:59:18 Tony Lindgren wrote: >> * Kalle Valo [170130 22:36]: [...] >> > * before distro updates linux-firmware create yours own deb/rpm/whatever >> > package

Re: [PATCH 4.10-rc3 05/13] net: bgmac: fix build errors when linux/phy*.h is removed from net/dsa.h

On 01/31/2017 08:18 PM, Russell King wrote: drivers/net/ethernet/broadcom/bgmac.c:1015:17: error: dereferencing pointer to incomplete type 'struct mii_bus' drivers/net/ethernet/broadcom/bgmac.c:1185:2: error: implicit declaration of function 'phy_start' [-Werror=implicit-function-declaration]

[patch] ipv6: pointer math error in ip6_tnl_parse_tlv_enc_lim()

Casting is a high precedence operation but "off" and "i" are in terms of bytes so we need to have some parenthesis here. Fixes: fbfa743a9d2a ("ipv6: fix ip6_tnl_parse_tlv_enc_lim()") Signed-off-by: Dan Carpenter diff --git a/net/ipv6/ip6_tunnel.c

Re: [PATCH net-next 00/10] bnxt_en: Add XDP support.

On Tue, Jan 31, 2017 at 10:22:12PM -0800, Alexei Starovoitov wrote: > On Tue, Jan 31, 2017 at 9:33 PM, Andy Gospodarek wrote: > > On Tue, Jan 31, 2017 at 10:36 AM, Andy Gospodarek > > wrote: > >> On Mon, Jan 30, 2017 at 08:47:47PM -0800, Alexei

Re: [PATCH v2 net-next] net: phy: Add LED mode driver for Microsemi PHYs.

On Wed, Feb 01, 2017 at 06:23:46PM +0530, Raju Lakkaraju wrote: > From: Raju Lakkaraju > > LED Mode: > Microsemi PHY support 2 LEDs (LED[0] and LED[1]) to display different > status information that can be selected by setting LED mode. > > LED Mode parameter

RE: [net-next 2/8] net/mlx5: Configure cache line size for start and end padding

From: Saeed Mahameed > Sent: 31 January 2017 20:59 > From: Daniel Jurgens > > There is a hardware feature that will pad the start or end of a DMA to > be cache line aligned to avoid RMWs on the last cache line. The default > cache line size setting for this feature is 64B.

Re: [PATCH v1 net-next] net: phy: Add LED mode driver for Microsemi PHYs.

Hi Raju, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Raju-Lakkaraju/net-phy-Add-LED-mode-driver-for-Microsemi-PHYs/20170201-185922 config: x86_64-randconfig-x001-201705 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901

[PATCH v2 net-next 0/3] Extract IFE logic to module

Extract ife logic from the tc_ife action into an independent module, and make the tc_ife action use it. This way, the ife encapsulation can be used by other modules other than tc_ife action. v1->v2: Fix duplicate symbol error by introducing a new patch that makes the original symbol static. The

[PATCH 3/3] net/sched: act_ife: Change to use ife module

Use the encode/decode functionality from the ife module instead of using implementation inside the act_ife. Reviewed-by: Jiri Pirko Signed-off-by: Yotam Gigi --- include/net/tc_act/tc_ife.h| 1 - include/uapi/linux/tc_act/tc_ife.h | 10 +---

[PATCH 1/3] net/sched: act_ife: Unexport ife_tlv_meta_encode

As the function ife_tlv_meta_encode is not used by any other module, unexport it and make it static for the act_ife module. Signed-off-by: Yotam Gigi --- include/net/tc_act/tc_ife.h | 2 -- net/sched/act_ife.c | 4 ++-- 2 files changed, 2 insertions(+), 4

[PATCH 2/3] net: Introduce ife encapsulation module

This module is responsible for the ife encapsulation protocol encode/decode logics. That module can: - ife_encode: encode skb and reserve space for the ife meta header - ife_decode: decode skb and extract the meta header size - ife_tlv_meta_encode - encodes one tlv entry into the reserved ife

RE: [net-next 1/8] net/mlx5: Fixed static checker warnings

From: Saeed Mahameed > Sent: 31 January 2017 20:59 > From: Or Gerlitz > > For some reason, sparse doesn't like using an expression of type (!x) > with a bitwise | and &. In order to mitigate that, we use a local > variable. > > Since getting a typeof(bitfield) is

[PATCH v2 net-next] net: phy: Add LED mode driver for Microsemi PHYs.

From: Raju Lakkaraju LED Mode: Microsemi PHY support 2 LEDs (LED[0] and LED[1]) to display different status information that can be selected by setting LED mode. LED Mode parameter (vsc8531, led-0-mode) and (vsc8531, led-1-mode) get from Device Tree.

Fwd: arch: arm: bpf: Converting cBPF to eBPF for arm 32 bit

Resending because of Formatting problems. Hi Kees & Daniel, On Tue, Jan 31, 2017 at 09:44:56AM -0800, Kees Cook wrote: > >> > 1.) Currently, as eBPF uses 64 bit registers, I am mapping 64 bit eBPF > >> > registers with 32 bit arm registers which looks wrong to me. Do anybody > >> > have some

[PATCH v1 net-next] net: phy: Add LED mode driver for Microsemi

From: Raju Lakkaraju LED Mode: Microsemi PHY support 2 LEDs (LED[0] and LED[1]) to display different status information that can be selected by setting LED mode. LED Mode parameter (vsc8531, led-0-mode) and (vsc8531, led-1-mode) get from Device Tree. Tested on

[PATCH v1 net-next] net: phy: Add LED mode driver for Microsemi PHYs.

From: Raju Lakkaraju LED Mode: Microsemi PHY support 2 LEDs (LED[0] and LED[1]) to display different status information that can be selected by setting LED mode. LED Mode parameter (vsc8531, led-0-mode) and (vsc8531, led-1-mode) get from Device Tree.

Re: [PATCH net] net: phy: Fix lack of reference count on PHY driver

On Wed, Feb 01, 2017 at 10:22:08AM +, Russell King - ARM Linux wrote: > On Tue, Jan 31, 2017 at 06:46:43PM -0800, Florian Fainelli wrote: > > From: Mao Wenan > > > > There is currently no reference count being held on the PHY driver, > > which makes it possible to remove

Bitte kontaktieren Sie mich für weitere Details!

Sehr geehrte Damen und Herren, Ich brauche Ihre Unterstützung in Ihrem Land zu verlagern und zu investieren.Ich bitte Sie um Hilfe, weil ich nicht das Wissen über Geschäft und die Regeln, die Ihr Land für eine sichere Investition führen. Werden Sie versprechen, mit mir aufrichtig zu sein?

  1   2   >