From: patchwork-bot+netdevbpf@kernel.org
To: Xiaolei Wang <xiaolei.wang@windriver.com>
Cc: pabeni@redhat.com, nicolas.ferre@microchip.com,
claudiu.beznea@tuxon.dev, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
rmk+kernel@armlinux.org.uk, Kexin.Hao@windriver.com,
Xiaolei.Wang@windriver.com, netdev@vger.kernel.org,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] net: macb: Relocate mog_init_rings() callback from macb_mac_link_up() to macb_open()
Date: Tue, 30 Dec 2025 10:30:08 +0000 [thread overview]
Message-ID: <176709060877.3205848.3719021860077682100.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251222015624.1994551-1-xiaolei.wang@windriver.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 22 Dec 2025 09:56:24 +0800 you wrote:
> In the non-RT kernel, local_bh_disable() merely disables preemption,
> whereas it maps to an actual spin lock in the RT kernel. Consequently,
> when attempting to refill RX buffers via netdev_alloc_skb() in
> macb_mac_link_up(), a deadlock scenario arises as follows:
>
> WARNING: possible circular locking dependency detected
> 6.18.0-08691-g2061f18ad76e #39 Not tainted
>
> [...]
Here is the summary with links:
- [net,v3] net: macb: Relocate mog_init_rings() callback from macb_mac_link_up() to macb_open()
https://git.kernel.org/netdev/net/c/99537d5c476c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-12-30 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 1:56 [PATCH net v3] net: macb: Relocate mog_init_rings() callback from macb_mac_link_up() to macb_open() Xiaolei Wang
2025-12-30 10:30 ` patchwork-bot+netdevbpf [this message]
2026-02-19 14:34 ` Alexander Dahl
2026-02-19 14:52 ` Kevin Hao
2026-02-19 15:36 ` Alexander Dahl
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=176709060877.3205848.3719021860077682100.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Kexin.Hao@windriver.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=stable@vger.kernel.org \
--cc=xiaolei.wang@windriver.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