From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, marc.dionne@auristor.com,
kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] rxrpc: Call state fixes
Date: Thu, 06 Feb 2025 03:00:31 +0000 [thread overview]
Message-ID: <173881083155.983395.4207821504706909846.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250204230558.712536-1-dhowells@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 4 Feb 2025 23:05:52 +0000 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] rxrpc: Fix call state set to not include the SERVER_SECURING state
https://git.kernel.org/netdev/net/c/41b996ce83bf
- [net,v2,2/2] rxrpc: Fix race in call state changing vs recvmsg()
https://git.kernel.org/netdev/net/c/2d7b30aef34d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-06 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 23:05 [PATCH net v2 0/2] rxrpc: Call state fixes David Howells
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 ` patchwork-bot+netdevbpf [this message]
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=173881083155.983395.4207821504706909846.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--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