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/8] rxrpc: Preparation for removal of use of skbs from AFS
Date: Tue, 30 Aug 2016 16:41:37 +0100 [thread overview]
Message-ID: <147257169706.6391.3116382288289485794.stgit@warthog.procyon.org.uk> (raw)
Here's a set of patches that prepare the way for the removal of the use of
sk_buffs from fs/afs (they'll be entirely retained within net/rxrpc):
(1) Fix a potential NULL-pointer deref in rxrpc_abort_calls().
(2) Condense all the terminal call state machine states to a single one
plus supplementary info.
(3) Add a trace point for rxrpc call usage debugging.
(4) Cleanups and missing headers.
(5) Provide a way for AFS to ask about a call's peer address without
having an sk_buff to query.
(6) Use call->peer directly rather than going via call->conn (which might
be NULL).
(7) Pass struct socket * to various rxrpc kernel interface functions so
they can use that directly rather than getting it from the rxrpc_call
struct.
The patches can be found here also (non-terminally on the branch):
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-20160830-1
David
---
David Howells (8):
rxrpc: Fix a potential NULL-pointer deref in rxrpc_abort_calls
rxrpc: Calls should only have one terminal state
rxrpc: Trace rxrpc_call usage
afs: Miscellaneous simple cleanups
afs: Need linux/random.h
rxrpc: Provide a way for AFS to ask for the peer address of a call
rxrpc: Use call->peer rather than going to the connection
rxrpc: Pass struct socket * to more rxrpc kernel interface functions
Documentation/networking/rxrpc.txt | 18 ++++-
fs/afs/cmservice.c | 26 +++----
fs/afs/internal.h | 5 +
fs/afs/main.c | 1
fs/afs/rxrpc.c | 28 ++++---
fs/afs/server.c | 11 ++-
include/net/af_rxrpc.h | 12 ++-
include/trace/events/rxrpc.h | 39 ++++++++++
net/rxrpc/af_rxrpc.c | 5 +
net/rxrpc/ar-internal.h | 135 +++++++++++++++++++++++++-----------
net/rxrpc/call_accept.c | 24 ++----
net/rxrpc/call_event.c | 63 +++++++----------
net/rxrpc/call_object.c | 133 +++++++++++++++++++++++++++--------
net/rxrpc/conn_client.c | 3 +
net/rxrpc/conn_event.c | 53 ++++++++------
net/rxrpc/conn_object.c | 4 +
net/rxrpc/input.c | 72 ++++++++++---------
net/rxrpc/output.c | 48 ++++++-------
net/rxrpc/peer_event.c | 25 +++++--
net/rxrpc/peer_object.c | 15 ++++
net/rxrpc/proc.c | 3 -
net/rxrpc/recvmsg.c | 13 ++-
net/rxrpc/skbuff.c | 4 -
23 files changed, 470 insertions(+), 270 deletions(-)
next reply other threads:[~2016-08-30 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 15:41 David Howells [this message]
2016-08-30 15:41 ` [PATCH net-next 1/8] rxrpc: Fix a potential NULL-pointer deref in rxrpc_abort_calls David Howells
2016-08-30 15:41 ` [PATCH net-next 2/8] rxrpc: Calls should only have one terminal state David Howells
2016-08-30 15:41 ` [PATCH net-next 3/8] rxrpc: Trace rxrpc_call usage David Howells
2016-08-30 15:42 ` [PATCH net-next 4/8] afs: Miscellaneous simple cleanups David Howells
2016-08-30 15:42 ` [PATCH net-next 5/8] afs: Need linux/random.h David Howells
2016-08-30 15:42 ` [PATCH net-next 6/8] rxrpc: Provide a way for AFS to ask for the peer address of a call David Howells
2016-08-30 15:42 ` [PATCH net-next 7/8] rxrpc: Use call->peer rather than going to the connection David Howells
2016-08-30 15:42 ` [PATCH net-next 8/8] rxrpc: Pass struct socket * to more rxrpc kernel interface functions David Howells
2016-08-31 5:09 ` [PATCH net-next 0/8] rxrpc: Preparation for removal of use of skbs from AFS 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=147257169706.6391.3116382288289485794.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).