syzbot


WARNING: suspicious RCU usage in __ipv6_dev_mc_dec

Status: closed as invalid on 2021/10/06 01:19
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 609d, last: 584d

Cause bisection: introduced by (bisect log) :
commit 997acaf6b4b59c6a9c259740312a69ea549cc684
Author: Mark Rutland <mark.rutland@arm.com>
Date: Mon Jan 11 15:37:07 2021 +0000

  lockdep: report broken irq restoration

Crash: WARNING in kvm_wait (log)
Repro: C syz .config

Fix bisection: fixed by (bisect log) [no-op commit]:
commit 3f3a9bc1f6df5a1a9ec39e3a5bee420328811be4
Author: Imre Deak <imre.deak@intel.com>
Date: Wed Mar 17 18:48:59 2021 +0000

  drm/i915/ilk-glk: Fix link training on links with LTTPRs


Sample crash report:
=============================
WARNING: suspicious RCU usage
5.12.0-rc4-syzkaller #0 Not tainted
-----------------------------
kernel/sched/core.c:8294 Illegal context switch in RCU-bh read-side critical section!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 1
4 locks held by kworker/0:4/4925:
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: atomic64_set include/asm-generic/atomic-instrumented.h:856 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: atomic_long_set include/asm-generic/atomic-long.h:41 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:616 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:643 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x871/0x1600 kernel/workqueue.c:2246
 #1: ffffc900016afda8 ((addr_chk_work).work){+.+.}-{0:0}, at: process_one_work+0x8a5/0x1600 kernel/workqueue.c:2250
 #2: ffffffff8d66d328 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0xa/0x20 net/ipv6/addrconf.c:4572
 #3: ffffffff8bf74300 (rcu_read_lock_bh){....}-{1:2}, at: addrconf_verify_rtnl+0x2b/0x1150 net/ipv6/addrconf.c:4459

stack backtrace:
CPU: 0 PID: 4925 Comm: kworker/0:4 Not tainted 5.12.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: ipv6_addrconf addrconf_verify_work
Call Trace:
 __dump_stack lib/dump_stack.c:79 [inline]
 dump_stack+0x141/0x1d7 lib/dump_stack.c:120
 ___might_sleep+0x229/0x2c0 kernel/sched/core.c:8294
 __mutex_lock_common kernel/locking/mutex.c:928 [inline]
 __mutex_lock+0xa9/0x1120 kernel/locking/mutex.c:1096
 __ipv6_dev_mc_dec+0x5f/0x340 net/ipv6/mcast.c:970
 addrconf_leave_solict net/ipv6/addrconf.c:2182 [inline]
 addrconf_leave_solict net/ipv6/addrconf.c:2174 [inline]
 __ipv6_ifa_notify+0x5b6/0xa90 net/ipv6/addrconf.c:6077
 ipv6_ifa_notify net/ipv6/addrconf.c:6100 [inline]
 ipv6_del_addr+0x463/0xae0 net/ipv6/addrconf.c:1294
 addrconf_verify_rtnl+0xd59/0x1150 net/ipv6/addrconf.c:4488
 addrconf_verify_work+0xf/0x20 net/ipv6/addrconf.c:4573
 process_one_work+0x98d/0x1600 kernel/workqueue.c:2275
 worker_thread+0x64c/0x1120 kernel/workqueue.c:2421
 kthread+0x3b1/0x4a0 kernel/kthread.c:292
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
BUG: sleeping function called from invalid context at kernel/locking/mutex.c:928
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 4925, name: kworker/0:4
4 locks held by kworker/0:4/4925:
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: atomic64_set include/asm-generic/atomic-instrumented.h:856 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: atomic_long_set include/asm-generic/atomic-long.h:41 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:616 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:643 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x871/0x1600 kernel/workqueue.c:2246
 #1: ffffc900016afda8 ((addr_chk_work).work){+.+.}-{0:0}, at: process_one_work+0x8a5/0x1600 kernel/workqueue.c:2250
 #2: ffffffff8d66d328 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0xa/0x20 net/ipv6/addrconf.c:4572
 #3: ffffffff8bf74300 (rcu_read_lock_bh){....}-{1:2}, at: addrconf_verify_rtnl+0x2b/0x1150 net/ipv6/addrconf.c:4459
Preemption disabled at:
[<ffffffff87b39f41>] local_bh_disable include/linux/bottom_half.h:19 [inline]
[<ffffffff87b39f41>] rcu_read_lock_bh include/linux/rcupdate.h:727 [inline]
[<ffffffff87b39f41>] addrconf_verify_rtnl+0x41/0x1150 net/ipv6/addrconf.c:4461
CPU: 0 PID: 4925 Comm: kworker/0:4 Not tainted 5.12.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: ipv6_addrconf addrconf_verify_work
Call Trace:
 __dump_stack lib/dump_stack.c:79 [inline]
 dump_stack+0x141/0x1d7 lib/dump_stack.c:120
 ___might_sleep.cold+0x1f1/0x237 kernel/sched/core.c:8328
 __mutex_lock_common kernel/locking/mutex.c:928 [inline]
 __mutex_lock+0xa9/0x1120 kernel/locking/mutex.c:1096
 __ipv6_dev_mc_dec+0x5f/0x340 net/ipv6/mcast.c:970
 addrconf_leave_solict net/ipv6/addrconf.c:2182 [inline]
 addrconf_leave_solict net/ipv6/addrconf.c:2174 [inline]
 __ipv6_ifa_notify+0x5b6/0xa90 net/ipv6/addrconf.c:6077
 ipv6_ifa_notify net/ipv6/addrconf.c:6100 [inline]
 ipv6_del_addr+0x463/0xae0 net/ipv6/addrconf.c:1294
 addrconf_verify_rtnl+0xd59/0x1150 net/ipv6/addrconf.c:4488
 addrconf_verify_work+0xf/0x20 net/ipv6/addrconf.c:4573
 process_one_work+0x98d/0x1600 kernel/workqueue.c:2275
 worker_thread+0x64c/0x1120 kernel/workqueue.c:2421
 kthread+0x3b1/0x4a0 kernel/kthread.c:292
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294

=============================
[ BUG: Invalid wait context ]
5.12.0-rc4-syzkaller #0 Tainted: G        W        
-----------------------------
kworker/0:4/4925 is trying to lock:
ffff88801aeef530 (&idev->mc_lock){+.+.}-{3:3}, at: __ipv6_dev_mc_dec+0x5f/0x340 net/ipv6/mcast.c:970
other info that might help us debug this:
context-{4:4}
4 locks held by kworker/0:4/4925:
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: atomic64_set include/asm-generic/atomic-instrumented.h:856 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: atomic_long_set include/asm-generic/atomic-long.h:41 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:616 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:643 [inline]
 #0: ffff8880211d7d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x871/0x1600 kernel/workqueue.c:2246
 #1: ffffc900016afda8 ((addr_chk_work).work){+.+.}-{0:0}, at: process_one_work+0x8a5/0x1600 kernel/workqueue.c:2250
 #2: ffffffff8d66d328 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0xa/0x20 net/ipv6/addrconf.c:4572
 #3: ffffffff8bf74300 (rcu_read_lock_bh){....}-{1:2}, at: addrconf_verify_rtnl+0x2b/0x1150 net/ipv6/addrconf.c:4459
stack backtrace:
CPU: 0 PID: 4925 Comm: kworker/0:4 Tainted: G        W         5.12.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: ipv6_addrconf addrconf_verify_work
Call Trace:
 __dump_stack lib/dump_stack.c:79 [inline]
 dump_stack+0x141/0x1d7 lib/dump_stack.c:120
 print_lock_invalid_wait_context kernel/locking/lockdep.c:4551 [inline]
 check_wait_context kernel/locking/lockdep.c:4612 [inline]
 __lock_acquire.cold+0x219/0x3b4 kernel/locking/lockdep.c:4850
 lock_acquire kernel/locking/lockdep.c:5510 [inline]
 lock_acquire+0x1ab/0x740 kernel/locking/lockdep.c:5475
 __mutex_lock_common kernel/locking/mutex.c:949 [inline]
 __mutex_lock+0x139/0x1120 kernel/locking/mutex.c:1096
 __ipv6_dev_mc_dec+0x5f/0x340 net/ipv6/mcast.c:970
 addrconf_leave_solict net/ipv6/addrconf.c:2182 [inline]
 addrconf_leave_solict net/ipv6/addrconf.c:2174 [inline]
 __ipv6_ifa_notify+0x5b6/0xa90 net/ipv6/addrconf.c:6077
 ipv6_ifa_notify net/ipv6/addrconf.c:6100 [inline]
 ipv6_del_addr+0x463/0xae0 net/ipv6/addrconf.c:1294
 addrconf_verify_rtnl+0xd59/0x1150 net/ipv6/addrconf.c:4488
 addrconf_verify_work+0xf/0x20 net/ipv6/addrconf.c:4573
 process_one_work+0x98d/0x1600 kernel/workqueue.c:2275
 worker_thread+0x64c/0x1120 kernel/workqueue.c:2421
 kthread+0x3b1/0x4a0 kernel/kthread.c:292
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294

Crashes (914):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-net-kasan-gce 2021/03/31 05:45 net-next 37f368d8d09d 6a81331a .config log report syz C WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/03/27 11:49 net-next a1281601f88e a8529b82 .config log report syz C WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/20 21:51 net-next e7ad33fa7bc5 c0ced557 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/20 17:42 net-next e7ad33fa7bc5 c0ced557 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/20 12:41 net-next e7ad33fa7bc5 c0ced557 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/20 11:07 net-next e7ad33fa7bc5 c0ced557 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/20 09:55 net-next e7ad33fa7bc5 4285c989 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/20 08:36 net-next e7ad33fa7bc5 4285c989 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/20 07:27 net-next e7ad33fa7bc5 4285c989 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/20 05:28 net-next e7ad33fa7bc5 4285c989 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/20 03:55 net-next e7ad33fa7bc5 4285c989 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/20 03:47 net-next e7ad33fa7bc5 4285c989 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 22:55 net-next e7ad33fa7bc5 4285c989 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 21:41 net-next e7ad33fa7bc5 50f523d7 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 20:16 net-next e7ad33fa7bc5 50f523d7 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 19:26 net-next e7ad33fa7bc5 50f523d7 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 18:14 net-next e7ad33fa7bc5 50f523d7 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 16:01 net-next e7ad33fa7bc5 50f523d7 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 15:01 net-next e7ad33fa7bc5 50f523d7 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 12:59 net-next e7ad33fa7bc5 50f523d7 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 10:52 net-next e7ad33fa7bc5 50f523d7 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 10:07 net-next e7ad33fa7bc5 50f523d7 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 08:20 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 06:59 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 05:48 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 04:31 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 04:13 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 01:44 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/19 00:38 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 22:42 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 20:59 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 19:22 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 18:04 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 16:33 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 15:32 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 14:44 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 13:35 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 11:53 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 10:48 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 09:36 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 08:19 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 04:39 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 03:36 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/04/18 02:09 net-next e7ad33fa7bc5 7e2b734b .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-net-kasan-gce 2021/03/27 07:11 net-next a1281601f88e a8529b82 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-linux-next-kasan-gce-root 2021/04/21 09:21 linux-next 1216f02e46a4 95777977 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-linux-next-kasan-gce-root 2021/04/20 14:06 linux-next 1216f02e46a4 c0ced557 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-linux-next-kasan-gce-root 2021/04/20 12:54 linux-next 1216f02e46a4 c0ced557 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-linux-next-kasan-gce-root 2021/04/20 01:58 linux-next 1216f02e46a4 4285c989 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
ci-upstream-linux-next-kasan-gce-root 2021/04/20 00:28 linux-next 1216f02e46a4 4285c989 .config log report info WARNING: suspicious RCU usage in __ipv6_dev_mc_dec
* Struck through repros no longer work on HEAD.