linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: netdev@vger.kernel.org
Cc: dhowells@redhat.com, linux-afs@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/4] rxrpc: Support IPv6
Date: Tue, 13 Sep 2016 23:41:31 +0100	[thread overview]
Message-ID: <147380649153.30728.6717292274642860064.stgit@warthog.procyon.org.uk> (raw)


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(-)

             reply	other threads:[~2016-09-13 22:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 22:41 David Howells [this message]
2016-09-13 22:41 ` [PATCH net-next 1/4] rxrpc: Create an address for sendmsg() to bind unbound socket with David Howells
2016-09-13 22:41 ` [PATCH net-next 2/4] rxrpc: Don't specify protocol to when creating transport socket David Howells
2016-09-13 22:41 ` [PATCH net-next 3/4] rxrpc: Use rxrpc_extract_addr_from_skb() rather than doing this manually David Howells
2016-09-13 22:41 ` [PATCH net-next 4/4] rxrpc: Add IPv6 support David Howells
2016-09-14  7:36 ` [PATCH net-next 0/4] rxrpc: Support IPv6 David Howells
2016-09-16  5:57 ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=147380649153.30728.6717292274642860064.stgit@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).