From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew+netdev@lunn.ch,
ms@dev.tdt.de, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com,
aleksander.lobakin@intel.com, linux-kernel@vger.kernel.org,
linux-x25@vger.kernel.org, bpf@vger.kernel.org,
syzbot+e67ea9c235b13b4f0020@syzkaller.appspotmail.com
Subject: Re: [PATCH net 1/2] net: lapbether: ignore ops-locked netdevs
Date: Fri, 08 Aug 2025 20:50:08 +0000 [thread overview]
Message-ID: <175468620854.263488.4481510843319056617.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250806213726.1383379-1-sdf@fomichev.me>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 6 Aug 2025 14:37:25 -0700 you wrote:
> Syzkaller managed to trigger lock dependency in xsk_notify via
> register_netdevice. As discussed in [0], using register_netdevice
> in the notifiers is problematic so skip adding lapbeth for ops-locked
> devices.
>
> xsk_notifier+0xa4/0x280 net/xdp/xsk.c:1645
> notifier_call_chain+0xbc/0x410 kernel/notifier.c:85
> call_netdevice_notifiers_info+0xbe/0x140 net/core/dev.c:2230
> call_netdevice_notifiers_extack net/core/dev.c:2268 [inline]
> call_netdevice_notifiers net/core/dev.c:2282 [inline]
> unregister_netdevice_many_notify+0xf9d/0x2700 net/core/dev.c:12077
> unregister_netdevice_many net/core/dev.c:12140 [inline]
> unregister_netdevice_queue+0x305/0x3f0 net/core/dev.c:11984
> register_netdevice+0x18f1/0x2270 net/core/dev.c:11149
> lapbeth_new_device drivers/net/wan/lapbether.c:420 [inline]
> lapbeth_device_event+0x5b1/0xbe0 drivers/net/wan/lapbether.c:462
> notifier_call_chain+0xbc/0x410 kernel/notifier.c:85
> call_netdevice_notifiers_info+0xbe/0x140 net/core/dev.c:2230
> call_netdevice_notifiers_extack net/core/dev.c:2268 [inline]
> call_netdevice_notifiers net/core/dev.c:2282 [inline]
> __dev_notify_flags+0x12c/0x2e0 net/core/dev.c:9497
> netif_change_flags+0x108/0x160 net/core/dev.c:9526
> dev_change_flags+0xba/0x250 net/core/dev_api.c:68
> devinet_ioctl+0x11d5/0x1f50 net/ipv4/devinet.c:1200
> inet_ioctl+0x3a7/0x3f0 net/ipv4/af_inet.c:1001
>
> [...]
Here is the summary with links:
- [net,1/2] net: lapbether: ignore ops-locked netdevs
https://git.kernel.org/netdev/net/c/53898ebabe84
- [net,2/2] hamradio: ignore ops-locked netdevs
https://git.kernel.org/netdev/net/c/c64237960819
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:[~2025-08-08 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 21:37 [PATCH net 1/2] net: lapbether: ignore ops-locked netdevs Stanislav Fomichev
2025-08-06 21:37 ` [PATCH net 2/2] hamradio: " Stanislav Fomichev
2025-08-08 20:50 ` 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=175468620854.263488.4481510843319056617.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=ms@dev.tdt.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=syzbot+e67ea9c235b13b4f0020@syzkaller.appspotmail.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