syzbot


linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge

Status: upstream: reported on 2022/03/04 10:41
Reported-by: syzbot+16e3f2c77e7c5a0113f9@syzkaller.appspotmail.com
Fix commit: f2aa197e4794 cgroup: Fix suspicious rcu_dereference_check() usage warning
Patched on: [ci-qemu-upstream ci-qemu-upstream-386 ci-qemu2-arm32 ci-qemu2-arm64 ci-qemu2-arm64-compat ci-qemu2-arm64-mte ci-upstream-bpf-kasan-gce ci-upstream-bpf-next-kasan-gce ci-upstream-gce-leak ci-upstream-kasan-gce ci-upstream-kasan-gce-386 ci-upstream-kasan-gce-root ci-upstream-kasan-gce-selinux-root ci-upstream-kasan-gce-smack-root ci-upstream-kmsan-gce ci-upstream-kmsan-gce-386 ci-upstream-linux-next-kasan-gce-root ci-upstream-net-kasan-gce ci-upstream-net-this-kasan-gce ci2-upstream-kcsan-gce ci2-upstream-usb], missing on: [ci-qemu2-riscv64]
First crash: 116d, last: 105d

Sample crash report:
=============================
WARNING: suspicious RCU usage
5.17.0-rc8-next-20220315-syzkaller #0 Not tainted
-----------------------------
include/linux/cgroup.h:494 suspicious rcu_dereference_check() usage!

other info that might help us debug this:


rcu_scheduler_active = 1, debug_locks = 1
2 locks held by kthreadd/2:
 #0: ffff8881401726e0 (&p->pi_lock){....}-{2:2}, at: task_rq_lock+0x63/0x360 kernel/sched/core.c:578
 #1: ffff8880b9c39f98 (&rq->__lock){-...}-{2:2}, at: raw_spin_rq_lock_nested+0x2b/0x120 kernel/sched/core.c:478

stack backtrace:
CPU: 0 PID: 2 Comm: kthreadd Not tainted 5.17.0-rc8-next-20220315-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 task_css include/linux/cgroup.h:494 [inline]
 task_ca kernel/sched/cpuacct.c:40 [inline]
 cpuacct_charge+0x2af/0x3c0 kernel/sched/cpuacct.c:342
 cgroup_account_cputime include/linux/cgroup.h:792 [inline]
 update_curr+0x37b/0x830 kernel/sched/fair.c:907
 dequeue_entity+0x23/0xfd0 kernel/sched/fair.c:4422
 dequeue_task_fair+0x238/0xea0 kernel/sched/fair.c:5771
 dequeue_task kernel/sched/core.c:2019 [inline]
 __do_set_cpus_allowed+0x186/0x960 kernel/sched/core.c:2508
 __set_cpus_allowed_ptr_locked+0x2ba/0x4e0 kernel/sched/core.c:2841
 __set_cpus_allowed_ptr kernel/sched/core.c:2874 [inline]
 set_cpus_allowed_ptr+0x78/0xa0 kernel/sched/core.c:2879
 kthreadd+0x44/0x750 kernel/kthread.c:724
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>

=============================
WARNING: suspicious RCU usage
5.17.0-rc8-next-20220315-syzkaller #0 Not tainted
-----------------------------
include/linux/cgroup.h:481 suspicious rcu_dereference_check() usage!

other info that might help us debug this:


rcu_scheduler_active = 1, debug_locks = 1
2 locks held by kthreadd/2:
 #0: ffff8881401726e0 (&p->pi_lock){....}-{2:2}, at: task_rq_lock+0x63/0x360 kernel/sched/core.c:578
 #1: ffff8880b9c39f98 (&rq->__lock){-...}-{2:2}, at: raw_spin_rq_lock_nested+0x2b/0x120 kernel/sched/core.c:478

stack backtrace:
CPU: 0 PID: 2 Comm: kthreadd Not tainted 5.17.0-rc8-next-20220315-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 task_css_set include/linux/cgroup.h:481 [inline]
 task_dfl_cgroup include/linux/cgroup.h:550 [inline]
 cgroup_account_cputime include/linux/cgroup.h:794 [inline]
 update_curr+0x671/0x830 kernel/sched/fair.c:907
 dequeue_entity+0x23/0xfd0 kernel/sched/fair.c:4422
 dequeue_task_fair+0x238/0xea0 kernel/sched/fair.c:5771
 dequeue_task kernel/sched/core.c:2019 [inline]
 __do_set_cpus_allowed+0x186/0x960 kernel/sched/core.c:2508
 __set_cpus_allowed_ptr_locked+0x2ba/0x4e0 kernel/sched/core.c:2841
 __set_cpus_allowed_ptr kernel/sched/core.c:2874 [inline]
 set_cpus_allowed_ptr+0x78/0xa0 kernel/sched/core.c:2879
 kthreadd+0x44/0x750 kernel/kthread.c:724
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>

Crashes (21):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-linux-next-kasan-gce-root 2022/03/15 13:27 linux-next a32cd981a6da 9e8eaa75 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/15 13:27 linux-next a32cd981a6da 9e8eaa75 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/15 13:27 linux-next a32cd981a6da 9e8eaa75 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/10 13:01 linux-next 71941773e143 9e8eaa75 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/10 13:01 linux-next 71941773e143 9e8eaa75 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/09 12:09 linux-next 4e7a74a6856f 9e8eaa75 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/09 12:09 linux-next 4e7a74a6856f 9e8eaa75 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/09 12:09 linux-next 4e7a74a6856f 9e8eaa75 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/08 16:18 linux-next cb153b68ff91 9e8eaa75 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/08 16:18 linux-next cb153b68ff91 9e8eaa75 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/08 16:18 linux-next cb153b68ff91 9e8eaa75 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/08 09:01 linux-next cb153b68ff91 7bdd8b2c .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/08 09:01 linux-next cb153b68ff91 7bdd8b2c .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/07 08:32 linux-next 519dd6c19986 7bdd8b2c .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/07 08:32 linux-next 519dd6c19986 7bdd8b2c .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/07 08:32 linux-next 519dd6c19986 7bdd8b2c .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/05 17:40 linux-next 6d284ba80c0c 7bdd8b2c .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/05 17:40 linux-next 6d284ba80c0c 7bdd8b2c .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/04 10:25 linux-next 6d284ba80c0c 45a13a73 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/04 10:25 linux-next 6d284ba80c0c 45a13a73 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge
ci-upstream-linux-next-kasan-gce-root 2022/03/04 10:25 linux-next 6d284ba80c0c 45a13a73 .config log report linux-next boot error: WARNING: suspicious RCU usage in cpuacct_charge