netdev - [PATCH v3 net-next 0/2] RDS-TCP: Network namespace support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <cover.1438752224.git.sowmini.varadhan@oracle.com>
Date:	Wed,  5 Aug 2015 01:43:24 -0400
From:	Sowmini Varadhan <sowmini.varadhan@...cle.com>
To:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:	davem@...emloft.net, rds-devel@....oracle.com,
	ajaykumar.hotchandani@...cle.com, igor.maximov@...cle.com,
	chien.yen@...cle.com, sowmini.varadhan@...cle.com,
	cwang@...pensource.com, dsahern@...il.com
Subject: [PATCH v3 net-next 0/2] RDS-TCP: Network namespace support

This patch series contains the set of changes to correctly set up 
the infra for PF_RDS sockets that use TCP as the transport in multiple
network namespaces.

Patch 1 in the series is the minimal set of changes to allow
a single instance of RDS-TCP to run in any (i.e init_net or other) net
namespace.  The changes in this patch set ensure that the execution of 
'modprobe [-r] rds_tcp' sets up the kernel TCP sockets 
relative to the current netns, so that RDS applications can send/recv
packets from that netns, and the netns can later be deleted cleanly.

Patch 2 of the series further allows multiple RDS-TCP instances,
one per network namespace. The changes in this patch allows dynamic
creation/tear-down of RDS-TCP client and server sockets  across all
current and future namespaces. 

v2 changes from RFC sent out earlier:
    David Ahern comments in patch 1, net_device notifier in patch 2, 
    patch 3 broken off and submitted separately.
v3: Cong Wang review comments.

Sowmini Varadhan (2):
  Make RDS-TCP work correctly when it is set up in a netns other than
    init_net
  Support multiple RDS-TCP listen endpoints, one per netns.

 net/rds/bind.c        |    3 +-
 net/rds/connection.c  |   16 +++--
 net/rds/ib.c          |    2 +-
 net/rds/ib_cm.c       |    5 +-
 net/rds/iw.c          |    2 +-
 net/rds/iw_cm.c       |    5 +-
 net/rds/rds.h         |   23 ++++++-
 net/rds/send.c        |    3 +-
 net/rds/tcp.c         |  165 +++++++++++++++++++++++++++++++++++++++++++-----
 net/rds/tcp.h         |    7 ++-
 net/rds/tcp_connect.c |    9 ++-
 net/rds/tcp_listen.c  |   40 ++++--------
 net/rds/transport.c   |    4 +-
 13 files changed, 214 insertions(+), 70 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html