Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1482832 > unrolled thread

[PATCH net-next 0/4] rxrpc: Support IPv6

Started byDavid Howells <dhowells@redhat.com>
First post2016-09-14 00:50 +0200
Last post2016-09-16 08:00 +0200
Articles 4 — 2 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH net-next 0/4] rxrpc: Support IPv6 David Howells <dhowells@redhat.com> - 2016-09-14 00:50 +0200
    [PATCH net-next 2/4] rxrpc: Don't specify protocol to when creating  transport socket David Howells <dhowells@redhat.com> - 2016-09-14 00:50 +0200
    Re: [PATCH net-next 0/4] rxrpc: Support IPv6 David Howells <dhowells@redhat.com> - 2016-09-14 09:40 +0200
    Re: [PATCH net-next 0/4] rxrpc: Support IPv6 David Miller <davem@davemloft.net> - 2016-09-16 08:00 +0200

#1482832 — [PATCH net-next 0/4] rxrpc: Support IPv6

FromDavid Howells <dhowells@redhat.com>
Date2016-09-14 00:50 +0200
Subject[PATCH net-next 0/4] rxrpc: Support IPv6
Message-ID<sh4GB-89a-9@gated-at.bofh.it>
Here is a set of patches that add IPv6 support.  They need to be applied on
top of the just-posted miscellaneous fix patches.  They are:

 (1) Make autobinding of an unconnected socket work when sendmsg() is
     called to initiate a client call.

 (2) Don't specify the protocol when creating the client socket, but rather
     take the default instead.

 (3) Use rxrpc_extract_addr_from_skb() in a couple of places that were
     doing the same thing manually.  This allows the IPv6 address
     extraction to be done in fewer places.

 (4) Add IPv6 support.  With this, calls can be made to IPv6 servers from
     userspace AF_RXRPC programs; AFS, however, can't use IPv6 yet as the
     RPC calls need to be upgradeable.

The patches can be found here also:

	http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rewrite

Tagged thusly:

	git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
	rxrpc-rewrite-20160913-2

David
---
David Howells (4):
      rxrpc: Create an address for sendmsg() to bind unbound socket with
      rxrpc: Don't specify protocol to when creating transport socket
      rxrpc: Use rxrpc_extract_addr_from_skb() rather than doing this manually
      rxrpc: Add IPv6 support


 net/rxrpc/af_rxrpc.c     |   27 ++++++++++-
 net/rxrpc/conn_object.c  |    8 +++
 net/rxrpc/local_event.c  |   13 ++---
 net/rxrpc/local_object.c |   39 +++++++---------
 net/rxrpc/output.c       |   48 +++++++++-----------
 net/rxrpc/peer_event.c   |   24 ++++++++++
 net/rxrpc/peer_object.c  |  109 +++++++++++++++++++++++++++++-----------------
 net/rxrpc/proc.c         |   30 +++++--------
 8 files changed, 179 insertions(+), 119 deletions(-)

[toc] | [next] | [standalone]


#1482834 — [PATCH net-next 2/4] rxrpc: Don't specify protocol to when creating transport socket

FromDavid Howells <dhowells@redhat.com>
Date2016-09-14 00:50 +0200
Subject[PATCH net-next 2/4] rxrpc: Don't specify protocol to when creating transport socket
Message-ID<sh4GB-89a-25@gated-at.bofh.it>
In reply to#1482832
Pass 0 as the protocol argument when creating the transport socket rather
than IPPROTO_UDP.

Signed-off-by: David Howells <dhowells@redhat.com>
---

 net/rxrpc/local_object.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/net/rxrpc/local_object.c b/net/rxrpc/local_object.c
index 782b9adf67cb..8720be2a6250 100644
--- a/net/rxrpc/local_object.c
+++ b/net/rxrpc/local_object.c
@@ -103,8 +103,8 @@ static int rxrpc_open_socket(struct rxrpc_local *local)
 	_enter("%p{%d}", local, local->srx.transport_type);
 
 	/* create a socket to represent the local endpoint */
-	ret = sock_create_kern(&init_net, PF_INET, local->srx.transport_type,
-			       IPPROTO_UDP, &local->socket);
+	ret = sock_create_kern(&init_net, local->srx.transport.family,
+			       local->srx.transport_type, 0, &local->socket);
 	if (ret < 0) {
 		_leave(" = %d [socket]", ret);
 		return ret;

[toc] | [prev] | [next] | [standalone]


#1483003

FromDavid Howells <dhowells@redhat.com>
Date2016-09-14 09:40 +0200
Message-ID<shcXw-6ki-21@gated-at.bofh.it>
In reply to#1482832
David Howells <dhowells@redhat.com> wrote:

> Here is a set of patches that add IPv6 support.  They need to be applied on
> top of the just-posted miscellaneous fix patches.  They are:

This subset needs to be made to depend on CONFIG_IPV6.

David

[toc] | [prev] | [next] | [standalone]


#1484689

FromDavid Miller <davem@davemloft.net>
Date2016-09-16 08:00 +0200
Message-ID<shUlP-ud-7@gated-at.bofh.it>
In reply to#1482832
From: David Howells <dhowells@redhat.com>
Date: Tue, 13 Sep 2016 23:41:31 +0100

> 
> Here is a set of patches that add IPv6 support.  They need to be applied on
> top of the just-posted miscellaneous fix patches.  They are:
> 
>  (1) Make autobinding of an unconnected socket work when sendmsg() is
>      called to initiate a client call.
> 
>  (2) Don't specify the protocol when creating the client socket, but rather
>      take the default instead.
> 
>  (3) Use rxrpc_extract_addr_from_skb() in a couple of places that were
>      doing the same thing manually.  This allows the IPv6 address
>      extraction to be done in fewer places.
> 
>  (4) Add IPv6 support.  With this, calls can be made to IPv6 servers from
>      userspace AF_RXRPC programs; AFS, however, can't use IPv6 yet as the
>      RPC calls need to be upgradeable.
 ...
> Tagged thusly:
> 
> 	git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> 	rxrpc-rewrite-20160913-2

Looks good, pulled, thanks.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web