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, horms@kernel.org, anderson@allelesecurity.com,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/3] rxrpc: Miscellaneous fixes
Date: Thu, 23 Apr 2026 21:50:10 +0000 [thread overview]
Message-ID: <177698101049.775674.1567171164890583654.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260423200909.3049438-1-dhowells@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 23 Apr 2026 21:09:05 +0100 you wrote:
> Here are some fixes for rxrpc, as found by Sashiko[1]:
>
> (1) Fix rxrpc_input_call_event() to only unshare DATA packets.
>
> (2) Fix re-decryption of RESPONSE packets where a partially decrypted
> skbuff gets requeued if there was a failure due to ENOMEM.
>
> [...]
Here is the summary with links:
- [net,1/3] rxrpc: Fix rxrpc_input_call_event() to only unshare DATA packets
https://git.kernel.org/netdev/net/c/55b2984c96c3
- [net,2/3] rxrpc: Fix re-decryption of RESPONSE packets
https://git.kernel.org/netdev/net/c/0422e7a4883f
- [net,3/3] rxrpc: Fix error handling in rxgk_extract_token()
https://git.kernel.org/netdev/net/c/3476c8bb960f
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:[~2026-04-23 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 20:09 [PATCH net 0/3] rxrpc: Miscellaneous fixes David Howells
2026-04-23 20:09 ` [PATCH net 1/3] rxrpc: Fix rxrpc_input_call_event() to only unshare DATA packets David Howells
2026-04-23 20:09 ` [PATCH net 2/3] rxrpc: Fix re-decryption of RESPONSE packets David Howells
2026-04-23 20:09 ` [PATCH net 3/3] rxrpc: Fix error handling in rxgk_extract_token() David Howells
2026-04-23 21:50 ` 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=177698101049.775674.1567171164890583654.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anderson@allelesecurity.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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