syzbot


BUG: scheduling while atomic in rtnl_lock

Status: premoderation: reported on 2024/04/27 09:08
Reported-by: syzbot+abda151e4ca580090427@syzkaller.appspotmail.com
First crash: 49d, last: 49d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-15 BUG: scheduling while atomic in rtnl_lock 1 86d 86d 0/2 premoderation: reported on 2024/03/20 15:06

Sample crash report:
BUG: scheduling while atomic: kworker/u4:7/27122/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81abd2dd>] free_percpu+0x9d/0x10f0 mm/percpu.c:2277
CPU: 1 PID: 27122 Comm: kworker/u4:7 Not tainted 6.1.75-syzkaller-00069-gfa87a072a7fc #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: netns cleanup_net
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
 dump_stack+0x15/0x1b lib/dump_stack.c:113
 __schedule_bug+0x195/0x260 kernel/sched/core.c:5960
 schedule_debug kernel/sched/core.c:5987 [inline]
 __schedule+0xcf7/0x1550 kernel/sched/core.c:6622
 schedule+0xc3/0x180 kernel/sched/core.c:6805
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6864
 mutex_optimistic_spin kernel/locking/mutex.c:529 [inline]
 __mutex_lock_common kernel/locking/mutex.c:629 [inline]
 __mutex_lock+0x5b6/0x1ca0 kernel/locking/mutex.c:774
 __mutex_lock_slowpath+0xe/0x10 kernel/locking/mutex.c:1063
 mutex_lock+0x130/0x1e0 kernel/locking/mutex.c:295
 rtnl_lock+0x15/0x20 net/core/rtnetlink.c:74
 ip_tunnel_delete_nets+0xca/0x380 net/ipv4/ip_tunnel.c:1121
 ipgre_exit_batch_net+0x22/0x30 net/ipv4/ip_gre.c:1028
 ops_exit_list net/core/net_namespace.c:174 [inline]
 cleanup_net+0x6c9/0xbf0 net/core/net_namespace.c:601
 process_one_work+0x73d/0xcb0 kernel/workqueue.c:2299
 worker_thread+0xa60/0x1260 kernel/workqueue.c:2446
 kthread+0x26d/0x300 kernel/kthread.c:386
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>
device bridge_slave_1 left promiscuous mode
bridge0: port 2(bridge_slave_1) entered disabled state
device bridge_slave_0 left promiscuous mode
bridge0: port 1(bridge_slave_0) entered disabled state
device veth1_macvtap left promiscuous mode

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/27 09:07 android14-6.1 fa87a072a7fc 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1 BUG: scheduling while atomic in rtnl_lock
* Struck through repros no longer work on HEAD.