From: patchwork-bot+netdevbpf@kernel.org
To: Rishikesh Jethwani <rjethwani@purestorage.com>
Cc: netdev@vger.kernel.org, john.fastabend@gmail.com,
sd@queasysnail.net, kuba@kernel.org, edumazet@kernel.org,
pabeni@redhat.com, horms@kernel.org
Subject: Re: [PATCH net] tls: device: protect async RX resync state during device-down
Date: Tue, 20 Oct 2026 19:40:22 +0000 [thread overview]
Message-ID: <179252522202.176933.15986245052236382358.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013213517.2219663-1-rjethwani@purestorage.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 13 Oct 2026 15:35:17 -0600 you wrote:
> tls_device_rx_resync_new_rec() can run in process context with the
> socket lock held, but without an RCU read lock: from the strparser work
> item (tls_strp_work()) and from the receive paths (tls_rx_rec_wait(),
> tls_rx_rec_done()). The resync_async pointer belongs to the driver RX
> context, which tls_device_down() tears down from the netdev notifier
> without taking the socket lock; only the softirq entry to the parser is
> implicitly inside an RCU section.
>
> [...]
Here is the summary with links:
- [net] tls: device: protect async RX resync state during device-down
https://git.kernel.org/netdev/net-next/c/f89a22812523
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-10-20 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 21:35 [PATCH net] tls: device: protect async RX resync state during device-down Rishikesh Jethwani
2026-10-20 19:40 ` 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=179252522202.176933.15986245052236382358.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rjethwani@purestorage.com \
--cc=sd@queasysnail.net \
/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