From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
willemb@google.com, horms@kernel.org, netdev@vger.kernel.org,
alex.aring@gmail.com
Subject: Re: [PATCH net-next] 6lowpan: nhc: use RCU instead of lowpan_nhc_lock
Date: Sat, 21 Nov 2026 02:00:27 +0000 [thread overview]
Message-ID: <179522642727.886068.16842769887373188114.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261118221820.1601273-1-edumazet@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 18 Nov 2026 23:18:20 +0100 you wrote:
> lowpan_nexthdr_nhcs[] is protected by lowpan_nhc_lock, a spinlock
> that is acquired with BH disabled for every compressed or uncompressed
> packet, even though the table only changes when an NHC module is
> loaded or unloaded.
>
> lowpan_nhc_del() already calls synchronize_net() after clearing
> its slot, so readers only need to be in an RCU read-side critical
> section to safely use a struct lowpan_nhc.
>
> [...]
Here is the summary with links:
- [net-next] 6lowpan: nhc: use RCU instead of lowpan_nhc_lock
https://git.kernel.org/netdev/net-next/c/111e1b0b985e
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-11-21 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 22:18 [PATCH net-next] 6lowpan: nhc: use RCU instead of lowpan_nhc_lock Eric Dumazet
2026-11-21 2: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=179522642727.886068.16842769887373188114.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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