From: David Howells <dhowells@redhat.com>
To: netdev@vger.kernel.org
Cc: David Howells <dhowells@redhat.com>,
Marc Dionne <marc.dionne@auristor.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH net v2 0/2] rxrpc: Call state fixes
Date: Tue, 4 Feb 2025 23:05:52 +0000 [thread overview]
Message-ID: <20250204230558.712536-1-dhowells@redhat.com> (raw)
Here some call state fixes for AF_RXRPC.
(1) Fix the state of a call to not treat the challenge-response cycle as
part of an incoming call's state set. The problem is that it makes
handling received of the final packet in the receive phase difficult
as that wants to change the call state - but security negotiations may
not yet be complete.
(2) Fix a race between the changing of the call state at the end of the
request reception phase of a service call, recvmsg() collecting the last
data and sendmsg() trying to send the reply before the I/O thread has
advanced the call state.
David
---
Changes
=======
ver #2)
- This was previously posted here[1] as patch 1, but I split out the broken
race fix, leaving the rest in the new patch 1 here. The race fix was
itself fixed and placed into the new patch 2.
The patches can be found here also:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-fixes
Link: https://lore.kernel.org/r/20250203110307.7265-2-dhowells@redhat.com/ [1]
David Howells (2):
rxrpc: Fix call state set to not include the SERVER_SECURING state
rxrpc: Fix race in call state changing vs recvmsg()
net/rxrpc/ar-internal.h | 2 +-
net/rxrpc/call_object.c | 6 ++----
net/rxrpc/conn_event.c | 4 +---
net/rxrpc/input.c | 12 ++++++++++--
net/rxrpc/sendmsg.c | 2 +-
5 files changed, 15 insertions(+), 11 deletions(-)
next reply other threads:[~2025-02-04 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 23:05 David Howells [this message]
2025-02-04 23:05 ` [PATCH net v2 1/2] rxrpc: Fix call state set to not include the SERVER_SECURING state David Howells
2025-02-04 23:05 ` [PATCH net v2 2/2] rxrpc: Fix race in call state changing vs recvmsg() David Howells
2025-02-06 3:00 ` [PATCH net v2 0/2] rxrpc: Call state fixes patchwork-bot+netdevbpf
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=20250204230558.712536-1-dhowells@redhat.com \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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