From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, kuniyu@google.com, netdev@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH net] net: fix backlog_unlock_irq_restore() vs CONFIG_PREEMPT_RT
Date: Tue, 17 Feb 2026 12:30:04 +0000 [thread overview]
Message-ID: <177133140483.55311.3255529638957203785.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260213120427.2914544-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 13 Feb 2026 12:04:27 +0000 you wrote:
> CONFIG_PREEMPT_RT is special, make this clear in backlog_lock_irq_save()
> and backlog_unlock_irq_restore().
>
> The issue shows up with CONFIG_DEBUG_IRQFLAGS=y
>
> raw_local_irq_restore() called with IRQs enabled
> WARNING: kernel/locking/irqflag-debug.c:10 at warn_bogus_irq_restore+0xc/0x20 kernel/locking/irqflag-debug.c:10, CPU#1: aoe_tx0/1321
> Modules linked in:
> CPU: 1 UID: 0 PID: 1321 Comm: aoe_tx0 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
> RIP: 0010:warn_bogus_irq_restore+0xc/0x20 kernel/locking/irqflag-debug.c:10
> Call Trace:
> <TASK>
> backlog_unlock_irq_restore net/core/dev.c:253 [inline]
> enqueue_to_backlog+0x525/0xcf0 net/core/dev.c:5347
> netif_rx_internal+0x120/0x550 net/core/dev.c:5659
> __netif_rx+0xa9/0x110 net/core/dev.c:5679
> loopback_xmit+0x43a/0x660 drivers/net/loopback.c:90
> __netdev_start_xmit include/linux/netdevice.h:5275 [inline]
> netdev_start_xmit include/linux/netdevice.h:5284 [inline]
> xmit_one net/core/dev.c:3864 [inline]
> dev_hard_start_xmit+0x2df/0x830 net/core/dev.c:3880
> __dev_queue_xmit+0x16f4/0x3990 net/core/dev.c:4829
> dev_queue_xmit include/linux/netdevice.h:3384 [inline]
>
> [...]
Here is the summary with links:
- [net] net: fix backlog_unlock_irq_restore() vs CONFIG_PREEMPT_RT
https://git.kernel.org/netdev/net/c/26f29b149169
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-02-17 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 12:04 [PATCH net] net: fix backlog_unlock_irq_restore() vs CONFIG_PREEMPT_RT Eric Dumazet
2026-02-17 12:30 ` 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=177133140483.55311.3255529638957203785.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.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