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/7] rxrpc: Miscellaneous changes
Date: Sat, 21 May 2022 08:45:08 +0100 [thread overview]
Message-ID: <165311910893.245906.4115532916417333325.stgit@warthog.procyon.org.uk> (raw)
Here are some miscellaneous changes for AF_RXRPC:
(1) Allow the list of local endpoints to be viewed through /proc.
(2) Switch to using refcount_t for refcounting.
(3) Fix a locking issue found by lockdep.
(4) Autogenerate tracing symbol enums from symbol->string maps to make it
easier to keep them in sync.
(5) Return an error to sendmsg() if a call it tried to set up failed.
Because it failed at this point, no notification will be generated for
recvmsg to pick up - but userspace still needs to know about the
failure.
(6) Fix the selection of abort codes generated by internal events. In
particular, rxrpc and kafs shouldn't be generating RX_USER_ABORT
unless it's because userspace did something to cancel a call.
(7) Adjust the interpretation and handling of certain ACK types to try and
detect NAT changes causing a call to seem to start mid-flow from a
different peer.
The patches are tagged here:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
rxrpc-next-20220521
and can also be found on the following branch:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-next
Tested-by: kafs-testing+fedora34_64checkkafs-build-493@auristor.com
Changes
=======
ver #2)
- Changed an rcu_dereference(->next) to list_head_next().
David
Link: https://lore.kernel.org/r/165306515409.34989.4713077338482294594.stgit@warthog.procyon.org.uk/ # v1
---
David Howells (7):
rxrpc: Allow list of in-use local UDP endpoints to be viewed in /proc
rxrpc: Use refcount_t rather than atomic_t
rxrpc: Fix locking issue
rxrpc: Automatically generate trace tag enums
rxrpc: Return an error to sendmsg if call failed
rxrpc, afs: Fix selection of abort codes
afs: Adjust ACK interpretation to try and cope with NAT
fs/afs/misc.c | 5 +-
fs/afs/rotate.c | 4 +
fs/afs/rxrpc.c | 8 +-
fs/afs/write.c | 1 +
fs/seq_file.c | 32 +++++
include/linux/list.h | 10 ++
include/linux/seq_file.h | 4 +
include/trace/events/rxrpc.h | 263 ++++++-----------------------------
net/rxrpc/af_rxrpc.c | 2 +-
net/rxrpc/ar-internal.h | 25 ++--
net/rxrpc/call_accept.c | 10 +-
net/rxrpc/call_event.c | 4 +-
net/rxrpc/call_object.c | 62 +++++----
net/rxrpc/conn_client.c | 30 ++--
net/rxrpc/conn_object.c | 51 +++----
net/rxrpc/conn_service.c | 8 +-
net/rxrpc/input.c | 31 ++++-
net/rxrpc/local_object.c | 68 ++++-----
net/rxrpc/net_ns.c | 7 +-
net/rxrpc/peer_object.c | 40 +++---
net/rxrpc/proc.c | 85 +++++++++--
net/rxrpc/sendmsg.c | 6 +
net/rxrpc/skbuff.c | 1 -
23 files changed, 366 insertions(+), 391 deletions(-)
next reply other threads:[~2022-05-21 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 7:45 David Howells [this message]
2022-05-21 7:45 ` [PATCH net-next 1/7] rxrpc: Allow list of in-use local UDP endpoints to be viewed in /proc David Howells
2022-05-21 7:45 ` [PATCH net-next 2/7] rxrpc: Use refcount_t rather than atomic_t David Howells
2022-05-21 7:45 ` [PATCH net-next 3/7] rxrpc: Fix locking issue David Howells
2022-05-21 7:45 ` [PATCH net-next 4/7] rxrpc: Automatically generate trace tag enums David Howells
2022-05-21 7:45 ` [PATCH net-next 5/7] rxrpc: Return an error to sendmsg if call failed David Howells
2022-05-21 7:45 ` [PATCH net-next 6/7] rxrpc, afs: Fix selection of abort codes David Howells
2022-05-21 7:45 ` [PATCH net-next 7/7] afs: Adjust ACK interpretation to try and cope with NAT David Howells
2022-05-22 20:40 ` [PATCH net-next 0/7] rxrpc: Miscellaneous changes patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2022-05-20 16:45 David Howells
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=165311910893.245906.4115532916417333325.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).