From: syzbot <syzbot+094799fb39e31554d5ee@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, horms@kernel.org,
jhs@mojatatu.com, jiri@resnulli.us, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
xiyou.wangcong@gmail.com
Subject: [syzbot] [net?] WARNING in rcu_note_context_switch (3)
Date: Thu, 14 Nov 2024 09:13:20 -0800 [thread overview]
Message-ID: <67362fb0.050a0220.2a2fcc.0069.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: de2f378f2b77 Merge tag 'nfsd-6.12-4' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11d654e8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=34db67f35f954904
dashboard link: https://syzkaller.appspot.com/bug?extid=094799fb39e31554d5ee
compiler: aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/384ffdcca292/non_bootable_disk-de2f378f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7f87c581ec66/vmlinux-de2f378f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/93ad0017ba33/Image-de2f378f.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+094799fb39e31554d5ee@syzkaller.appspotmail.com
------------[ cut here ]------------
Voluntary context switch within RCU read-side critical section!
WARNING: CPU: 1 PID: 62 at kernel/rcu/tree_plugin.h:331 rcu_note_context_switch+0x354/0x49c kernel/rcu/tree_plugin.h:331
Modules linked in:
CPU: 1 UID: 0 PID: 62 Comm: kworker/u8:3 Not tainted 6.12.0-rc6-syzkaller-00279-gde2f378f2b77 #0
Hardware name: linux,dummy-virt (DT)
Workqueue: bond0 bond_mii_monitor
pstate: 614000c9 (nZCv daIF +PAN -UAO -TCO +DIT -SSBS BTYPE=--)
pc : rcu_note_context_switch+0x354/0x49c kernel/rcu/tree_plugin.h:331
lr : rcu_note_context_switch+0x354/0x49c kernel/rcu/tree_plugin.h:331
sp : ffff800082f7ba00
x29: ffff800082f7ba00 x28: 0000000000000003 x27: f3f0000004214900
x26: 0000000000000000 x25: fff000007f8ee800 x24: 0000000000000000
x23: 0000000000000000 x22: f3f0000004214900 x21: 0000000000000000
x20: ffff8000827006c0 x19: fff000007f8ef6c0 x18: fffffffffffdbe58
x17: fff07ffffd1ef000 x16: ffff800080008000 x15: 0000000000000048
x14: fffffffffffdbea0 x13: ffff80008274e5d0 x12: 00000000000012cc
x11: 0000000000000644 x10: ffff800082807c30 x9 : ffff80008274e5d0
x8 : 00000000ffffdfff x7 : ffff8000827fe5d0 x6 : 0000000000000644
x5 : fff000007f8e43c8 x4 : 40000000ffffe644 x3 : fff07ffffd1ef000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : f3f0000004214900
Call trace:
rcu_note_context_switch+0x354/0x49c kernel/rcu/tree_plugin.h:331
__schedule+0xb8/0x8fc kernel/sched/core.c:6570
__schedule_loop kernel/sched/core.c:6767 [inline]
schedule+0x34/0x104 kernel/sched/core.c:6782
synchronize_rcu_expedited+0x17c/0x1f0 kernel/rcu/tree_exp.h:991
synchronize_net+0x18/0x34 net/core/dev.c:11286
dev_deactivate_many+0x120/0x278 net/sched/sch_generic.c:1377
dev_deactivate+0x60/0xac net/sched/sch_generic.c:1403
linkwatch_do_dev+0x78/0xec net/core/link_watch.c:175
linkwatch_sync_dev+0x8c/0xc8 net/core/link_watch.c:263
ethtool_op_get_link+0x18/0x34 net/ethtool/ioctl.c:62
bond_check_dev_link+0x68/0x154 drivers/net/bonding/bond_main.c:873
bond_miimon_inspect drivers/net/bonding/bond_main.c:2717 [inline]
bond_mii_monitor+0x110/0x91c drivers/net/bonding/bond_main.c:2939
process_one_work+0x15c/0x29c kernel/workqueue.c:3229
process_scheduled_works kernel/workqueue.c:3310 [inline]
worker_thread+0x24c/0x354 kernel/workqueue.c:3391
kthread+0x114/0x118 kernel/kthread.c:389
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
---[ end trace 0000000000000000 ]---
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2024-11-14 17:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=67362fb0.050a0220.2a2fcc.0069.GAE@google.com \
--to=syzbot+094799fb39e31554d5ee@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@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;
as well as URLs for NNTP newsgroup(s).