From: Johannes Berg <johannes@sipsolutions.net>
To: syzbot <syzbot+3647b9259b77c1bb8e94@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Cc: Jay Vosburgh <jv@jvosburgh.net>
Subject: Re: [syzbot] [wireless?] BUG: sleeping function called from invalid context in wext_netdev_notifier_call
Date: Thu, 12 Dec 2024 09:52:44 +0100 [thread overview]
Message-ID: <301ccb4cf2451c748d2b9b68648be7cfadf75c6a.camel@sipsolutions.net> (raw)
In-Reply-To: <675a6973.050a0220.17f54a.0050.GAE@google.com>
On Wed, 2024-12-11 at 20:41 -0800, syzbot wrote:
> CPU: 1 UID: 0 PID: 12894 Comm: kworker/u8:18 Not tainted 6.13.0-rc1-syzkaller-00183-g4c49f38e20a5 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
> Workqueue: bond0 bond_mii_monitor
> Call Trace:
> <TASK>
> __dump_stack lib/dump_stack.c:94 [inline]
> dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
> __might_resched+0x5d4/0x780 kernel/sched/core.c:8758
> down_read+0x8e/0xa40 kernel/locking/rwsem.c:1523
> wireless_nlevent_flush net/wireless/wext-core.c:351 [inline]
> wext_netdev_notifier_call+0x1f/0x120 net/wireless/wext-core.c:371
> notifier_call_chain+0x1a5/0x3f0 kernel/notifier.c:85
> netdev_state_change+0x11f/0x1a0 net/core/dev.c:1378
> linkwatch_do_dev+0x112/0x170 net/core/link_watch.c:182
> ethtool_op_get_link+0x15/0x60 net/ethtool/ioctl.c:62
> bond_check_dev_link+0x1f1/0x3f0 drivers/net/bonding/bond_main.c:873
> bond_miimon_inspect drivers/net/bonding/bond_main.c:2740 [inline]
> bond_mii_monitor+0x49a/0x3170 drivers/net/bonding/bond_main.c:2962
Yeah this isn't new. I thought we were going to just squash this with
https://lore.kernel.org/netdev/2730097.1721581672@famine/
Whatever came of that?
johannes
next prev parent reply other threads:[~2024-12-12 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 4:41 [syzbot] [wireless?] BUG: sleeping function called from invalid context in wext_netdev_notifier_call syzbot
2024-12-12 8:52 ` Johannes Berg [this message]
2024-12-13 8:36 ` Kuniyuki Iwashima
2024-12-13 8:39 ` Johannes Berg
2024-12-13 8:45 ` Kuniyuki Iwashima
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=301ccb4cf2451c748d2b9b68648be7cfadf75c6a.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jv@jvosburgh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+3647b9259b77c1bb8e94@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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