Re: [PATCH] net: udp: add socket option to report RX queue level

On 03/17/2017 05:01 PM, Eric Dumazet wrote: On Fri, 2017-03-17 at 14:13 -0700, Chris Kuiper wrote: This adds a new socket option "SO_RXQ_ALLOC" that enables providing the RX queue buffer allocation as ancillary data from the recvmsg() system call. The value reported is a byte number and

[PATCH net-next v4 2/2]L2TP:Adjust intf MTU, add underlay L3, L2 hdrs

In existing kernel code, when setting up the L2TP interface, all of the tunnel encapsulation headers are not taken into account when setting up the MTU on the L2TP logical interface device. Due to this, the packets created by the applications on top of the L2TP layer are larger than they ought

[PATCH net 3/4] ibmvnic: Move ibmvnic adapter intialization to its own routine

The intialization of the ibmvnic driver with respect to the virtual server it connects to should be moved to its own routine. This will alolow the driver to initiate this process from places outside of the drivers probe routine. Signed-off-by: Nathan Fontenot ---

Re: [PATCH net-next v3 1/2]L2TP:Adjust intf MTU, add underlay L3, L2 hdrs

[Posting a v4 patch-set shortly based on additional code review comments received in internal review, please disregard the v3 patches] On Thu, Mar 16, 2017 at 9:33 PM, R. Parameswaran wrote: > > > In existing kernel code, when setting up the L2TP interface, all of the

SO_BINDTODEVICE in VRFs not working?

Hello, I'm writing an application that should listen on a TCP port bound to an inteface in a VRF. The bind/listen sequence is the following: int s = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP); char *ifname = "eth1"; setsockopt(s, SOL_SOCKET, SO_BINDTODEVICE, ifname, strlen(ifname)+1);

[PATCH net-next v4 1/2]L2TP:Adjust intf MTU, add underlay L3, L2 hdrs

In existing kernel code, when setting up the L2TP interface, all of the tunnel encapsulation headers are not taken into account when setting up the MTU on the L2TP logical interface device. Due to this, the packets created by the applications on top of the L2TP layer are larger than they ought

[PATCH net 2/4] ibmvnic: Move login to its own routine

Move the code that handles login and renegotiation of ibmvnic capabilities to its own routine. Signed-off-by: Nathan Fontenot --- drivers/net/ethernet/ibm/ibmvnic.c | 28 1 file changed, 20 insertions(+), 8 deletions(-) diff --git

[PATCH net 4/4] ibmvnic: Correct ibmvnic handling of device open/close

When closing the ibmvnic device we need to release the resources used in communicating to the virtual I/O server. These need to be re-negotiated with the server at open time. This patch moves the releasing of resources a separate routine and updates the open and close handlers to release all

[PATCH] net: vrf: Reset rt6i_idev in local dst after put

The VRF driver takes a reference to the inet6_dev on the VRF device for its rt6_local dst when handling local traffic through the VRF device as a loopback. When the device is deleted the driver does a put on the idev but does not reset rt6i_idev in the rt6_info struct. When the dst is destroyed,

[PATCH iproute2] ip route: Add missing space between nexthop and via for mpls multipath routes

MPLS multipath routes are missing a space between 'nexthop' and 'via': $ ip -net ns1 -f mpls ro ls 100 nexthopvia inet 172.16.2.2 dev virt12 nexthopvia inet 172.16.3.2 dev br0 Add it. Signed-off-by: David Ahern --- ip/iproute.c | 2 +- 1 file

[PATCH] rhashtable: Add rhashtable_lookup_get_insert_fast

Add rhashtable_lookup_get_insert_fast for fixed keys, similar to rhashtable_lookup_get_insert_key for explicit keys. Signed-off-by: Andreas Gruenbacher Acked-by: Herbert Xu --- include/linux/rhashtable.h | 22 ++ 1 file

[PATCH net 0/4] ibmvnic: Initialization fixes and improvements

These patches resolve issues with the ibmvnic initialization process. John Allen (1): ibmvnic: Move login and queue negotiation into ibmvnic_open Nathan Fontenot (3): ibmvnic: Move login to its own routine ibmvnic: Move ibmvnic adapter intialization to its own routine ibmvnic: Correct

[PATCH net-next] liquidio: fix for vf mac addr command sent to nic firmware

From: Rick Farrington Change to support host<->firmware command return value. Fix for vf mac addr state command. 1. Added support for firmware commands to return a value: - previously, the returned code overlapped with host codes, thus commands were only

[PATCH] net: usb: pegasus: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. As I don't have the hardware, I'd be very pleased if someone may test this patch. Signed-off-by: Philippe Reynes --- drivers/net/usb/pegasus.c | 14 -- 1

[PATCH net 1/4] ibmvnic: Move login and queue negotiation into ibmvnic_open

VNIC server expects LINK_STATE_UP to be sent within 30s of the login. If we exceed the timeout, VNIC server will attempt to fail over. Since time between probe and open of the device is indeterminate, move login and queue negotiation into ibmvnic open so we can guarantee that login and sending

Re: [PATCH] net: udp: add socket option to report RX queue level

On Fri, 2017-03-17 at 14:13 -0700, Chris Kuiper wrote: > This adds a new socket option "SO_RXQ_ALLOC" that enables providing > the RX queue buffer allocation as ancillary data from the recvmsg() > system call. The value reported is a byte number and together with > the RX queue size (obtained via

[PATCH v3] net: sun: sungem: rix a possible null dereference

The function gem_begin_auto_negotiation dereference the pointer ep before testing if it's null. This patch add a check on ep before dereferencing it. Fixes: 92552fdda557 ("net: sun: sungem: use new api ethtool_{get|set}_link_ksettings") Reported-by: Dan Carpenter

Re: [PATCH net-next] ipv6: Implement optimized IPv6 masked address comparison for ARM64

That's clearly not right - I'm not sure quite what undefined behaviour assumption convinces GCC to optimise the whole thing away> While the pointer casting is a bit ghastly, I don't actually think that GCC is taking advantage of undefined behaviour here, rather it looks like you have a

[PATCH v4 2/2] can: spi: hi311x: Add Holt HI-311x CAN driver

This patch adds support for the Holt HI-311x CAN controller. The HI311x CAN controller is capable of transmitting and receiving standard data frames, extended data frames and remote frames. The HI311x interfaces with the host over SPI. Datasheet: www.holtic.com/documents/371-hi-3110_v-rev-jpdf.do

[PATCH] net: udp: add socket option to report RX queue level

This adds a new socket option "SO_RXQ_ALLOC" that enables providing the RX queue buffer allocation as ancillary data from the recvmsg() system call. The value reported is a byte number and together with the RX queue size (obtained via getsockopt(SO_RCVBUF) can be used to calculate a percentage

[PATCH v4 1/2] can: holt_hi311x: document device tree bindings

Document the HOLT HI-311x CAN device tree bindings. Signed-off-by: Akshay Bhat Acked-by: Rob Herring --- v3 -> v4: - No changes .../devicetree/bindings/net/can/holt_hi311x.txt| 24 ++ 1 file changed, 24 insertions(+) create mode

[PATCH] bna: integer overflow bug in debugfs

We could allocate less memory than intended because we do: bnad->regdata = kzalloc(len << 2, GFP_KERNEL); The shift can overflow leading to a crash. This is debugfs code so the impact is very small. Fixes: 7afc5dbde091 ("bna: Add debugfs interface.") Signed-off-by: Dan Carpenter

[net-next 05/13] igb: Limit maximum frame Rx based on MTU

From: Alexander Duyck In order to support the use of build_skb going forward it will be necessary to place a maximum limit on the amount of data we can receive when jumbo frames is not enabled. In order to do this I am adding a new upper limit for receive based on

[net-next 06/13] igb: Only sync size of expected frame in ethtool testing

From: Alexander Duyck We only need to sync the size of the frame that is read to test. We don't need to sync the entire Rx buffer. This way the testing is more consistent with how we handle things in the receive path. Signed-off-by: Alexander Duyck

[net-next 04/13] igb: Don't bother clearing Tx buffer_info in igb_clean_tx_ring

From: Alexander Duyck In the case of the Tx rings we need to only clear the Tx buffer_info when we are resetting the rings. Ideally we do this when we configure the ring to bring it back up instead of when we are taking it down in order to avoid dirtying pages we

[net-next 08/13] igb: Add support for ethtool private flag to allow use of legacy Rx

From: Alexander Duyck Since there are potential drawbacks to the new Rx allocation approach I thought it best to add a "chicken bit" so that we can turn the feature off if in the event that a problem is found. It also provides a means of validating the legacy Rx

[net-next 01/13] igb: Add support for DMA_ATTR_WEAK_ORDERING

From: Alexander Duyck Since we are already using DMA attributes in igb for Rx there is no reason why we can't also apply DMA_ATTR_WEAK_ORDERING which is needed on some platforms to improve performance. Signed-off-by: Alexander Duyck

[net-next 07/13] igb: Use page_address offset from page instead of masking virtual address

From: Alexander Duyck Update the handling of page addresses so that we always refer to them using a void pointer, and try to use the consistent name of va indicating we are working with a virtual address. Signed-off-by: Alexander Duyck

[net-next 00/13][pull request] 1GbE Intel Wired LAN Driver Updates 2017-03-17

This series contains updates to mainly igb, with one fix for ixgbe. Alex does all the changes in the series, starting with adding support for DMA_ATTR_WEAK_ORDERING to improve performance on some platforms. Modified igb to use the length of the packet instead of the DD status bit to determine if

[net-next 09/13] igb: Add support for using order 1 pages to receive large frames

From: Alexander Duyck This patch adds support for using 3K buffers in order 1 pages the same way we were using 2K buffers in 4K pages. We are reserving 1K of room for now to have space available for future headroom and tailroom when we enable build_skb support. One

[net-next 13/13] igb/ixgbe: Fix typo in igb_build_skb and/or ixgbe_build_skb code comment

From: Alexander Duyck There was a typo that I had left in the code comments for the igb and ixgbe functions that enabled build_skb support. Signed-off-by: Alexander Duyck Tested-by: Aaron Brown Signed-off-by:

[net-next 10/13] igb: Add support for padding packet

From: Alexander Duyck With the size of the frame limited we can now write to an offset within the buffer instead of having to write at the very start of the buffer. The advantage to this is that it allows us to leave padding room for things like supporting XDP in

[net-next 11/13] igb: Break out Rx buffer page management

From: Alexander Duyck At this point we have 2 to 3 paths that can be taken depending on what Rx modes are enabled. In order to better support that and improve the maintainability I am breaking out the common bits from those paths and making them into their own

[net-next 03/13] igb: Clear Rx buffer_info in configure instead of clean

From: Alexander Duyck This change makes it so that instead of going through the entire ring on Rx cleanup we only go through the region that was designated to be cleaned up and stop when we reach the region where new allocations should start. In addition we can

[net-next 12/13] igb: Re-add support for build_skb in igb

From: Alexander Duyck This reverts commit f9d40f6a9921 ("igb: Revert support for build_skb in igb") and adds a few changes to update it to work with the latest version of igb. We are now able to revert the removal of this due to the fact that with the recent changes

[net-next 02/13] igb: Use length to determine if descriptor is done

From: Alexander Duyck This change makes it so that we use the length of the packet instead of the DD status bit to determine if a new descriptor is ready to be processed. The obvious advantage is that it cuts down on reads as we don't really even need the DD bit if

Re: [PATCH v2 2/2] can: spi: hi311x: Add Holt HI-311x CAN driver

Hi Wolfgang, On 03/17/2017 01:04 PM, Wolfgang Grandegger wrote: > > Hm, that's unusual. Cable disconnected and then send a message: > > $ grep /proc/interrupts; sleep 10; /proc/interrupts > > should make things clear. But maybe it's a clever chip and it does stop > sending error messages if

[PATCH net-next] liquidio: add debug error messages to report command timeout

From: Rick Farrington Add timeout error message in lio_process_ordered_list(). Add host failure status in existing error message in if_cfg_callback(). Signed-off-by: Rick Farrington Signed-off-by: Felix Manlunas

Re: [PATCH 3/4] uapi glibc compat: Do not check for __USE_MISC

On 03/16/2017 09:26 AM, Mikko Rapeli wrote: > On Thu, Mar 16, 2017 at 07:59:12AM +, David Woodhouse wrote: >> On Sun, 2017-03-12 at 23:00 +0100, Hauke Mehrtens wrote: >>> __USE_MISC is glibc specific and not available in musl libc. Only do >>> this check when glibc is used. This fixes a

[PATCH net-next] liquidio: remove duplicate code

From: Satanand Burla Remove code duplicated in PF and VF; define that code once only in a common header file included by PF and VF. Signed-off-by: Satanand Burla Signed-off-by: Felix Manlunas ---

Re: ip_auto_config() prevents network device to be registered

Hello, On 01/31/2017 02:49 PM, Javier Martinez Canillas wrote: > > The kernelci folks pointed out that a Samsung Exynos based board was failing > to boot when trying to mount the rootfs via NFS, due a networking issue [0]. > > I looked at the issue and it turned out to be a race between

Re: [PATCH v2 2/2] can: spi: hi311x: Add Holt HI-311x CAN driver

Hi Akshay, Am 17.03.2017 um 17:00 schrieb Akshay Bhat: Hi Wolfgang, On 03/17/2017 03:39 AM, Wolfgang Grandegger wrote: Hello Akshay, Am 16.03.2017 um 23:29 schrieb Akshay Bhat: Hi Wolfgang, On 03/16/2017 04:02 PM, Wolfgang Grandegger wrote: Looks much better now! There are message for

Re: [PATCH v2 2/2] can: spi: hi311x: Add Holt HI-311x CAN driver

Hi Wolfgang, On 03/17/2017 03:39 AM, Wolfgang Grandegger wrote: > Hello Akshay, > > Am 16.03.2017 um 23:29 schrieb Akshay Bhat: >> Hi Wolfgang, >> >> On 03/16/2017 04:02 PM, Wolfgang Grandegger wrote: >>> >>> Looks much better now! There are message for state changes to error >>> warning and

[PATCH net,stable] qmi_wwan: add Dell DW5811e

This is a Dell branded Sierra Wireless EM7455. It is operating in MBIM mode by default, but can be configured to provide two QMI/RMNET functions. Signed-off-by: Bjørn Mork --- Note regarding stable backports: This device should only be added to v4.5 and later. It depends on

[PATCH v2 net-next 3/3] net: stmmac: RX queue routing configuration

This patch adds the configuration of RX queues' routing. Signed-off-by: Joao Pinto --- changes v1->v2: - DT bindings were changed to bool - DT parsing was simplified, improving routing parameter scalability Documentation/devicetree/bindings/net/stmmac.txt | 6

[PATCH v2 net-next 1/3] net: stmmac: enable multiple buffers

This patch creates 2 new structures (stmmac_tx_queue and stmmac_rx_queue) in include/linux/stmmac.h, enabling that each RX and TX queue has its own buffers and data. Signed-off-by: Joao Pinto --- changes v1->v2: - just to keep up version

[PATCH v2 net-next 0/3] net: stmmac: adding multiple buffers and routing

As agreed with David Miller, this patch-set is the third and last to enable multiple queues in stmmac. This third one focuses on: a) Enable multiple buffering to the driver and queue independent data b) Configuration of RX and TX queues' priority c) Configuration of RX queues' routing Joao

[PATCH v2 net-next 2/3] net: stmmac: TX and RX queue priority configuration

This patch adds the configuration of RX and TX queues' priority. Signed-off-by: Joao Pinto --- changes v1->v2: - added range value info in the DT bindings Documentation/devicetree/bindings/net/stmmac.txt | 5 +++ drivers/net/ethernet/stmicro/stmmac/common.h | 4

Re: [PATCH 07/17] net: convert sock.sk_refcnt from atomic_t to refcount_t

On Fri, 2017-03-17 at 07:42 +, Reshetova, Elena wrote: > Should we then first measure the actual numbers to understand what we > are talking here about? > I would be glad to do it if you suggest what is the correct way to do > measurements here to actually reflect the real life use cases.

Admin

ATENCIÓN; Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de correo electrónico. Para revalidar su buzón de

De groeten

De groeten In een korte inleiding, ik ben advocaat Rodrigo Venancio, uit Portugal maar momenteel woonachtig in Londen, ik stuurde u een e-mail met betrekking tot uw overleden familielid, maar ik heb geen reactie van u ontvangen, overledene is een burger van uw land met dezelfde achternaam met je,

[PATCH net] sch_dsmark: fix invalid skb_cow() usage

From: Eric Dumazet skb_cow(skb, sizeof(ip header)) is not very helpful in this context. First we need to use pskb_may_pull() to make sure the ip header is in skb linear part, then use skb_try_make_writable() to address clones issues. Fixes: 4c30719f4f55 ("[PKT_SCHED]

Re: [PATCH 01/23] net, sunrpc: convert rpc_cred.cr_count from atomic_t to refcount_t

On Fri, 2017-03-17 at 09:02 -0400, Jeff Layton wrote: > On Fri, 2017-03-17 at 12:50 +, Trond Myklebust wrote: > > On Fri, 2017-03-17 at 14:10 +0200, Elena Reshetova wrote: > > > refcount_t type and corresponding API should be > > > used instead of atomic_t when the variable is used as > > > a

Re: [PATCH net] bridge: ebtables: fix reception of frames DNAT-ed to bridge device

On Wed, Mar 15, 2017 at 11:06:05PM +0100, Pablo Neira Ayuso wrote: > On Wed, Mar 15, 2017 at 10:16:19PM +0100, Linus Lüssing wrote: > > On Wed, Mar 15, 2017 at 07:15:39PM +0100, Pablo Neira Ayuso wrote: > > > Could you update ebtables dnat to check if the ethernet address > > > matches the one of

Re: [PATCH 01/23] net, sunrpc: convert rpc_cred.cr_count from atomic_t to refcount_t

On Fri, 2017-03-17 at 12:50 +, Trond Myklebust wrote: > On Fri, 2017-03-17 at 14:10 +0200, Elena Reshetova wrote: > > refcount_t type and corresponding API should be > > used instead of atomic_t when the variable is used as > > a reference counter. This allows to avoid accidental > >

Re: [PATCH 01/23] net, sunrpc: convert rpc_cred.cr_count from atomic_t to refcount_t

On Fri, 2017-03-17 at 14:10 +0200, Elena Reshetova wrote: > refcount_t type and corresponding API should be > used instead of atomic_t when the variable is used as > a reference counter. This allows to avoid accidental > refcounter overflows that might lead to use-after-free > situations. > >

Re: [PATCH net-next] ipv6: Implement optimized IPv6 masked address comparison for ARM64

On Fri, Mar 17, 2017 at 12:00:42PM +, Robin Murphy wrote: > On 17/03/17 04:42, Subash Abhinov Kasiviswanathan wrote: > > Android devices use multiple ip[6]tables for statistics, UID matching > > and other functionality. Perf output indicated that ip6_do_table > > was taking a considerable

[PATCH 13/23] net, xfrm: convert xfrm_state.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 12/23] net, x25: convert x25_neigh.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 11/23] net, x25: convert x25_route.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 23/23] net, ax25: convert ax25_cb.refcount from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 21/23] net, ax25: convert ax25_uid_assoc.refcount from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 18/23] net, sctp: convert sctp_chunk.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 19/23] net, sctp: convert sctp_transport.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 09/23] net, rds: convert rds_mr.r_refcount from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 20/23] net, sctp: convert sctp_ep_common.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 10/23] net, rds: convert rds_message.m_refcount from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 15/23] net, xfrm: convert sec_path.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 22/23] net, ax25: convert ax25_route.refcount from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 16/23] net, sctp: convert sctp_auth_bytes.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 08/23] net, rds: convert rds_incoming.i_refcount from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 14/23] net, xfrm: convert xfrm_policy.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 17/23] net, sctp: convert sctp_datamsg.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 04/23] net, ceph: convert ceph_snap_context.nref from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

Re: [RESEND PATCH -net] cpsw/netcp: work around reverse cpts dependency

On Fri, Mar 17, 2017 at 4:13 AM, David Miller wrote: > > I'm fine with this change, but please keep the user visible Kconfig > symbol name the same, use the new name for the internal one. Yes, makes snese. > I know that this means you have to make more changes elsewhere in

[PATCH 03/23] net, sunrpc: convert gss_upcall_msg.count from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 06/23] net, ceph: convert ceph_pagelist.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 07/23] net, rds: convert rds_ib_device.refcount from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 00/23] various networking refcount conversions, part 2

This series, for the rest of network subsystem components, replaces atomic_t reference counters with the new refcount_t type and API (see include/linux/refcount.h). By doing this we prevent intentional or accidental underflows or overflows that can led to use-after-free vulnerabilities. The

[PATCH 05/23] net, ceph: convert ceph_osd.o_ref from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 01/23] net, sunrpc: convert rpc_cred.cr_count from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 02/23] net, sunrpc: convert gss_cl_ctx.count from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

Re: [PATCH net-next] ipv6: Implement optimized IPv6 masked address comparison for ARM64

On 17/03/17 04:42, Subash Abhinov Kasiviswanathan wrote: > Android devices use multiple ip[6]tables for statistics, UID matching > and other functionality. Perf output indicated that ip6_do_table > was taking a considerable amount of CPU and more that ip_do_table > for an equivalent rate.

Could you please let me know if you receive my last email, introducing myself to you, on a ( Business Opportunity)? I urgently wish to know if we can work together.

Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Omit unnecessary memset of netdev private data

On Freitag, 17. März 2017 12:08:59 CET Tobias Klauser wrote: > The memory for netdev_priv is allocated using kzalloc in alloc_netdev > (or alloc_netdev_mq respectively) so there is no need to set it to 0 > again. > > Signed-off-by: Tobias Klauser > --- >

Re: [GIT PULL 0/5] IPVS Updates for v4.12

On Thu, Mar 16, 2017 at 01:43:10PM +0100, Simon Horman wrote: > Hi Pablo, > > please consider these enhancements to the IPVS for v4.12. > > * Update sysctl documentation > * Remove unnecessary printk in __ip_vs_init > > The following changes since commit

Re: [PATCH net-next 3/3] net: stmmac: RX queue routing configuration

Às 5:12 PM de 3/16/2017, Florian Fainelli escreveu: > On 03/16/2017 03:56 AM, Joao Pinto wrote: >> This patch adds the configuration of RX queues' routing. >> >> Signed-off-by: Joao Pinto >> --- >> Documentation/devicetree/bindings/net/stmmac.txt | 19 ++- >>

[PATCH 00/18] net subsystem various refcounter conversions

This series, for various network subsystem components, replaces atomic_t reference counters with the new refcount_t type and API (see include/linux/refcount.h). By doing this we prevent intentional or accidental underflows or overflows that can led to use-after-free vulnerabilities. The patches

RE: [PATCH net-next] r8152: simply the arguments

From: Hayes Wang > Sent: 17 March 2017 03:00 > To: David Laight; netdev@vger.kernel.org > Cc: nic_swsd; linux-ker...@vger.kernel.org; linux-...@vger.kernel.org > Subject: RE: [PATCH net-next] r8152: simply the arguments > > David Laight [mailto:david.lai...@aculab.com] > > Sent: Thursday, March

[PATCH 04/18] net, vxlan: convert vxlan_sock.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 02/18] net, l2tp: convert l2tp_tunnel.ref_count from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 01/18] net, llc: convert llc_sap.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 03/18] net, l2tp: convert l2tp_session.ref_count from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 07/18] net, atm: convert atm_dev.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 09/18] net, atm: convert in_cache_entry.use from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 08/18] net, atm: convert lec_arp_table.usage from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 14/18] net, lapb: convert lapb_cb.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

Re: [PATCH net-next 2/3] net: stmmac: TX and RX queue priority configuration

Às 4:55 PM de 3/16/2017, Florian Fainelli escreveu: > On 03/16/2017 03:56 AM, Joao Pinto wrote: >> This patch adds the configuration of RX and TX queues' priority. >> >> Signed-off-by: Joao Pinto >> --- >> Documentation/devicetree/bindings/net/stmmac.txt | 5 +++ >>

[PATCH 17/18] net, netrom: convert nr_neigh.refcount from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH 16/18] net, ipx: convert ipx_route.refcnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

  1   2   >