Re: [Patch net-next] net_sched: add network namespace support for tc actions

On Sat, Feb 20, 2016 at 10:36 AM, Daniel Borkmann wrote: > > Do you see a way to reduce the code duplication needed across all > the action modules? I.e. that each of them now needs to register > a new per netns subsystem, etc. In other words, is there a way the > action API

Re: [PATCH] jme: remove the jme driver as it is no longer maintained

On Sat, Feb 20, 2016 at 10:16 PM, David Miller wrote: > > Sorry, this is not how things work. > > You can suggest marking the driver unmaintained in MAINTAINERS if the > listed developer has been unresponsive for a very long time. > > But removing the driver altogether is not

Re: [Patch net] net_sched: fix memory leaks when rmmod tc action modules

On Fri, Feb 19, 2016 at 4:06 PM, Cong Wang wrote: > We only release the memory of the hashtable itself, not its > entries inside. We need to do both. > > Cc: Jamal Hadi Salim > Signed-off-by: Cong Wang Hmm, after a second

Re: [PATCH] jme: remove the jme driver as it is no longer maintained

Sorry, this is not how things work. You can suggest marking the driver unmaintained in MAINTAINERS if the listed developer has been unresponsive for a very long time. But removing the driver altogether is not prudent at all. Just because it doesn't work %100 the way you like, and nobody has

[PATCH] rtlwifi: pass struct rtl_stats by reference as it is more efficient

From: Colin Ian King passing rtl_stats by value is inefficient; the structure is over 300 bytes in size and generally just one field (packet_report_type) is being accessed, so the pass by value is a relatively large overhead. This change just affects just the

[PATCH] jme: remove the jme driver as it is no longer maintained

This driver also breaks my suspend/resume support, see the link below for details: https://bugzilla.kernel.org/show_bug.cgi?id=112351 If you choose to keep this garbage, move it to staging at least, where it belongs. Signed-off-by: Diego Viola --- MAINTAINERS

Re: r8169 nic sometimes doesn't work after changing the mac address

On Saturday 12 December 2015 22:43:45 Maximilian Engelhardt wrote: > Hello, > > I'm using a Lenovo TinkPad Edge E135 notebook that has a Realtek wired > network interface inbuilt. Under some conditions the nic doesn't work after > changing the mac address. > > It took me some time to figure out

[PATCH v3] net: ethernet: davicom: fix devicetree irq resource

The dm9000 driver doesn't work in at least one device-tree configuration, spitting an error message on irq resource : [1.062495] dm9000 800.ethernet: insufficient resources [1.068439] dm9000 800.ethernet: not found (-2). [1.073451] dm9000: probe of 800.ethernet failed with

Re: [net-next PATCH 0/2] GENEVE/VXLAN: Enable outer Tx checksum by default

On Fri, Feb 19, 2016 at 6:18 PM, Jesse Gross wrote: > On Fri, Feb 19, 2016 at 4:14 PM, Tom Herbert wrote: >> On Fri, Feb 19, 2016 at 4:08 PM, Jesse Gross wrote: >>> On Fri, Feb 19, 2016 at 3:10 PM, Alex Duyck wrote:

Re: [Patch net-next] net_sched: add network namespace support for tc actions

On 02/20/2016 01:43 AM, Cong Wang wrote: Currently tc actions are stored in a per-module hashtable, therefore are visible to all network namespaces. This is probably the last part of the tc subsystem which is not aware of netns now. This patch makes them per-netns, several tc action API's need

pull request: bluetooth 2016-02-20

Hi Dave, Here's an important patch for 4.5 which fixes potential invalid pointer access when processing completed Bluetooth HCI commands. Please let me know if there are any issues pulling. Thanks. Johan --- The following changes since commit d07c0278da1f4cfc91c3d46d0d07a0d13a949892: net:

[PATCH] Add Dell Wireless 5809e Gobi 4G HSPA+ Mobile Broadband Card (rev3) to qmi_wwan

New revison of Dell Wireless 5809e Gobi 4G HSPA+ Mobile Broadband Card has new idProduct Bus 002 Device 006: ID 413c:81b3 Dell Computer Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 bDeviceSubClass

[PATCH V7] netfilter: h323: avoid potential attack

I think hackers chould build a malicious h323 packet to overflow the pointer p which will panic during the memcpy(addr, p, len) For example, he may fabricate a very large taddr->ipAddress.ip in function get_h225_addr. To avoid above, I add buffer boundary checking both in get addr functions and

Re: [PATCH] xen-netfront: set real_num_tx_queues to zreo avoid to trigger BUG_ON

On 02/20/2016 04:27 AM, Gonglei wrote: It's possible for a race condition to exist between xennet_open() and talk_to_netback(). After invoking netfront_probe() then other threads or processes invoke xennet_open (such as NetworkManager) immediately may trigger BUG_ON(). Besides, we also should

Re: [PATCH] net: smc911x: convert pxa dma to dmaengine

Hi, On Sat, 20 Feb 2016, Hitoshi Mitake wrote: > > Hi Robert, > > At Sat, 06 Feb 2016 10:05:51 +0100, > Robert Jarzmik wrote: > > > > David Miller writes: > > > > > From: Robert Jarzmik > > > Date: Fri, 05 Feb 2016 22:44:56 +0100 > > > > > >>

RE: [PATCH iproute2] bridge: add support for dynamic fdb entries

+1 Rami Rosen Intel Corporation

Re: [PATCH 1/1] net-next: do not store needed_headroom in ip_tunnel_xmit

On Fri, Feb 19, 2016 at 8:26 PM, Francesco Ruggeri wrote: > Misconfigurations can result in local tunnel loops being created. > __dev_queue_xmit catches packets caught in a loop and drops them, > but the affected tunnels' needed_headroom can be corrupted in the > process as

Re: [PATCH] net: smc911x: convert pxa dma to dmaengine

Hitoshi Mitake writes: > Hi Robert, > > On Sat, Feb 6, 2016 at 6:05 PM, Robert Jarzmik wrote: > > Please just keep pinging people to properly test this. > > Okay, let's have another try. > > Hi Guennadi, Hitoshi, Fabio, >

pull-request: can-next 2016-02-20

-can-next.git tags/linux-can-next-for-4.6-20160220 for you to fetch changes up to 0c4d9c94a1303008b32079991360cea7ab849ef3: can: ifi: Add IFI CANFD IP support (2016-02-20 14:56:15 +0100) linux-can-next-for-4.6-20160220

Re: [PATCH] net: smc911x: convert pxa dma to dmaengine

Hi Robert, At Sat, 06 Feb 2016 10:05:51 +0100, Robert Jarzmik wrote: > > David Miller writes: > > > From: Robert Jarzmik > > Date: Fri, 05 Feb 2016 22:44:56 +0100 > > > >> Apart from Alberto who answered he cannot test it by lack of hardware, the

[net-next][PATCH 03/13] MAINTAINERS: update RDS entry

Acked-by: Chien Yen Signed-off-by: Santosh Shilimkar Signed-off-by: Santosh Shilimkar --- MAINTAINERS | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index

[net-next][PATCH 12/13] RDS: IB: allocate extra space on queues for FRMR support

Fastreg MR(FRMR) memory registration and invalidation makes use of work request and completion queues for its operation. Patch allocates extra queue space towards these operation(s). Signed-off-by: Santosh Shilimkar Signed-off-by: Santosh Shilimkar

[net-next][PATCH 01/13] RDS: Drop stale iWARP RDMA transport

RDS iWarp support code has become stale and non testable. As indicated earlier, am dropping the support for it. If new iWarp user(s) shows up in future, we can adapat the RDS IB transprt for the special RDMA READ sink case. iWarp needs an MR for the RDMA READ sink. Signed-off-by: Santosh

[net-next][PATCH 09/13] RDS: IB: handle the RDMA CM time wait event

Drop the RDS connection on RDMA_CM_EVENT_TIMEWAIT_EXIT so that it can reconnect and resume. While testing fastreg, this error happened in couple of tests but was getting un-noticed. Signed-off-by: Santosh Shilimkar Signed-off-by: Santosh Shilimkar

[net-next][PATCH 10/13] RDS: IB: add mr reused stats

Add MR reuse statistics to RDS IB transport. Signed-off-by: Santosh Shilimkar Signed-off-by: Santosh Shilimkar --- net/rds/ib.h | 2 ++ net/rds/ib_rdma.c | 7 ++- net/rds/ib_stats.c | 2 ++ 3 files changed, 10 insertions(+), 1

[net-next][PATCH 04/13] RDS: IB: Remove the RDS_IB_SEND_OP dependency

This helps to combine asynchronous fastreg MR completion handler with send completion handler. No functional change. Signed-off-by: Santosh Shilimkar Signed-off-by: Santosh Shilimkar --- net/rds/ib.h | 1 - net/rds/ib_cm.c | 42

[net-next][PATCH 07/13] RDS: IB: move FMR code to its own file

No functional change. Signed-off-by: Santosh Shilimkar Signed-off-by: Santosh Shilimkar --- net/rds/ib_fmr.c | 126 +- net/rds/ib_mr.h | 6 +++ net/rds/ib_rdma.c | 105

[net-next][PATCH 13/13] RDS: IB: Support Fastreg MR (FRMR) memory registration mode

From: Avinash Repaka Fastreg MR(FRMR) is another method with which one can register memory to HCA. Some of the newer HCAs supports only fastreg mr mode, so we need to add support for it to RDS to have RDS functional on them. Some of the older HCAs support both FMR and

[net-next][PATCH 08/13] RDS: IB: add connection info to ibmr

Preperatory patch for FRMR support. From connection info, we can retrieve cm_id which contains qp handled needed for work request posting. We also need to drop the RDS connection on QP error states where connection handle becomes useful. Signed-off-by: Santosh Shilimkar

[net-next][PATCH 06/13] RDS: IB: create struct rds_ib_fmr

Keep fmr related filed in its own struct. Fastreg MR structure will be added to the union. Signed-off-by: Santosh Shilimkar Signed-off-by: Santosh Shilimkar --- net/rds/ib_fmr.c | 17 ++--- net/rds/ib_mr.h | 11 +--

[net-next][PATCH 00/13] RDS: Major clean-up with couple of new features for 4.6

Series is generated against net-next but also applies against Linus's tip cleanly. The diff-stat looks bit scary since almost ~4K lines of code is getting removed. Brief summary of the series: - Drop the stale iWARP support: RDS iWarp support code has become stale and non testable for

[net-next][PATCH 11/13] RDS: IB: add Fastreg MR (FRMR) detection support

Discovere Fast Memmory Registration support using IB device IB_DEVICE_MEM_MGT_EXTENSIONS. Certain HCA might support just FRMR or FMR or both FMR and FRWR. In case both mr type are supported, default FMR is used. Using module parameter 'prefer_frmr', user can choose its preferred MR method for RDS.

[net-next][PATCH 05/13] RDS: IB: Re-organise ibmr code

No functional changes. This is in preperation towards adding fastreg memory resgitration support. Signed-off-by: Santosh Shilimkar Signed-off-by: Santosh Shilimkar --- net/rds/Makefile | 2 +- net/rds/ib.c | 37 +++--- net/rds/ib.h

[net-next][PATCH 02/13] RDS: Add support for SO_TIMESTAMP for incoming messages

The SO_TIMESTAMP generates time stamp for each incoming RDS messages User app can enable it by using SO_TIMESTAMP setsocketopt() at SOL_SOCKET level. CMSG data of cmsg type SO_TIMESTAMP contains the time stamp in struct timeval format. Reviewed-by: Sowmini Varadhan

Re: [PATCHv3 net 5/5] nfp: don't trust netif_running() in debug code

On 2/20/16, David Miller wrote: > From: Jakub Kicinski > Date: Thu, 18 Feb 2016 20:38:13 + > >> Since change_mtu() can fail and leave us with netif_running() >> returning true even though all rings were freed - we should >> look at

[PATCH] fmvj18x_cs: fix incorrect indexing of dev->dev_addr[] when copying the MAC address

fix incorrect indexing of dev->dev_addr[] when copying the MAC address of FMV-J182 at buf[5]. Signed-off-by: Ken Kawasaki --- --- linux-4.4.1/drivers/net/ethernet/fujitsu/fmvj18x_cs.c.orig 2016-02-19 20:48:40.143852346 +0900 +++

[PATCH net-next] i40e: remove broken link.

This patch removes a broken link from Documentation/networking/i40e.txt. Signed-off-by: Rami Rosen --- Documentation/networking/i40e.txt | 9 - 1 file changed, 9 deletions(-) diff --git a/Documentation/networking/i40e.txt b/Documentation/networking/i40e.txt index

Re: [PATCH] Bluetooth: hci_core: cancel power off delayed work properly

Hi Wei-Ning, > When the HCI_AUTO_OFF flag is cleared, the power_off delayed work need > to be cancel or HCI will be powered off even if it's managed. > > Signed-off-by: Wei-Ning Huang > --- > net/bluetooth/hci_core.c | 1 + > 1 file changed, 1 insertion(+) patch has been

Re: [PATCH] Bluetooth: hci_core: Avoid mixing up req_complete and req_complete_skb

Hi Douglas, > In commit 44d271377479 ("Bluetooth: Compress the size of struct > hci_ctrl") we squashed down the size of the structure by using a union > with the assumption that all users would use the flag to determine > whether we had a req_complete or a req_complete_skb. > > Unfortunately we