From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, linux-rt-devel@lists.linux.dev,
davem@davemloft.net, andrew+netdev@lunn.ch, spasswolf@web.de,
clrkwllms@kernel.org, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, rostedt@goodmis.org
Subject: Re: [PATCH net] net: Provide a PREEMPT_RT specific check for netdev_queue::_xmit_lock
Date: Thu, 05 Mar 2026 11:20:06 +0000 [thread overview]
Message-ID: <177270960605.2657587.18286685206790931125.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260302162631.uGUyIqDT@linutronix.de>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 2 Mar 2026 17:26:31 +0100 you wrote:
> After acquiring netdev_queue::_xmit_lock the number of the CPU owning
> the lock is recorded in netdev_queue::xmit_lock_owner. This works as
> long as the BH context is not preemptible.
>
> On PREEMPT_RT the softirq context is preemptible and without the
> softirq-lock it is possible to have multiple user in __dev_queue_xmit()
> submitting a skb on the same CPU. This is fine in general but this means
> also that the current CPU is recorded as netdev_queue::xmit_lock_owner.
> This in turn leads to the recursion alert and the skb is dropped.
>
> [...]
Here is the summary with links:
- [net] net: Provide a PREEMPT_RT specific check for netdev_queue::_xmit_lock
https://git.kernel.org/netdev/net/c/b824c3e16c19
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-03-05 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 16:26 [PATCH net] net: Provide a PREEMPT_RT specific check for netdev_queue::_xmit_lock Sebastian Andrzej Siewior
2026-03-02 16:49 ` -EXT-[PATCH " Soderlund, David
2026-03-05 11:20 ` 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=177270960605.2657587.18286685206790931125.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
--cc=spasswolf@web.de \
/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