From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <stfomichev@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
willemdebruijn.kernel@gmail.com, horms@kernel.org,
linux-kernel@vger.kernel.org,
syzbot+b191b5ccad8d7a986286@syzkaller.appspotmail.com
Subject: Re: [PATCH net v2] af_packet: move notifier's packet_dev_mc out of rcu critical section
Date: Tue, 27 May 2025 13:50:28 +0000 [thread overview]
Message-ID: <174835382850.1645024.12860246850484744014.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250522031129.3247266-1-stfomichev@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 21 May 2025 20:11:28 -0700 you wrote:
> Syzkaller reports the following issue:
>
> BUG: sleeping function called from invalid context at kernel/locking/mutex.c:578
> __mutex_lock+0x106/0xe80 kernel/locking/mutex.c:746
> team_change_rx_flags+0x38/0x220 drivers/net/team/team_core.c:1781
> dev_change_rx_flags net/core/dev.c:9145 [inline]
> __dev_set_promiscuity+0x3f8/0x590 net/core/dev.c:9189
> netif_set_promiscuity+0x50/0xe0 net/core/dev.c:9201
> dev_set_promiscuity+0x126/0x260 net/core/dev_api.c:286 packet_dev_mc net/packet/af_packet.c:3698 [inline]
> packet_dev_mclist_delete net/packet/af_packet.c:3722 [inline]
> packet_notifier+0x292/0xa60 net/packet/af_packet.c:4247
> notifier_call_chain+0x1b3/0x3e0 kernel/notifier.c:85
> call_netdevice_notifiers_extack net/core/dev.c:2214 [inline]
> call_netdevice_notifiers net/core/dev.c:2228 [inline]
> unregister_netdevice_many_notify+0x15d8/0x2330 net/core/dev.c:11972
> rtnl_delete_link net/core/rtnetlink.c:3522 [inline]
> rtnl_dellink+0x488/0x710 net/core/rtnetlink.c:3564
> rtnetlink_rcv_msg+0x7cf/0xb70 net/core/rtnetlink.c:6955
> netlink_rcv_skb+0x219/0x490 net/netlink/af_netlink.c:2534
>
> [...]
Here is the summary with links:
- [net,v2] af_packet: move notifier's packet_dev_mc out of rcu critical section
https://git.kernel.org/netdev/net/c/d8d85ef0a631
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-05-27 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 3:11 [PATCH net v2] af_packet: move notifier's packet_dev_mc out of rcu critical section Stanislav Fomichev
2025-05-22 17:06 ` Willem de Bruijn
2025-05-27 13: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=174835382850.1645024.12860246850484744014.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stfomichev@gmail.com \
--cc=syzbot+b191b5ccad8d7a986286@syzkaller.appspotmail.com \
--cc=willemdebruijn.kernel@gmail.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