Hello, syzbot found the following issue on: HEAD commit: aa486552a110 Merge tag 'memblock-v6.12-rc1' of git://git.k.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10ae0507980000 kernel config: https://syzkaller.appspot.com/x/.config?x=6c71bad3e6ab6955 dashboard link: https://syzkaller.appspot.com/bug?extid=d41f74db64598e0b5016 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=170c659f980000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14a7caa9980000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/7c6beec63de3/disk-aa486552.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/fa35efb3dd39/vmlinux-aa486552.xz kernel image: https://storage.googleapis.com/syzbot-assets/537d8ff45d85/bzImage-aa486552.xz The issue was bisected to: commit 5f6bd380c7bdbe10f7b4e8ddcceed60ce0714c6d Author: Peter Zijlstra <peterz@xxxxxxxxxxxxx> Date: Mon May 27 12:06:55 2024 +0000 sched/rt: Remove default bandwidth control bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15684507980000 final oops: https://syzkaller.appspot.com/x/report.txt?x=17684507980000 console output: https://syzkaller.appspot.com/x/log.txt?x=13684507980000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+d41f74db64598e0b5016@xxxxxxxxxxxxxxxxxxxxxxxxx Fixes: 5f6bd380c7bd ("sched/rt: Remove default bandwidth control") INFO: task kworker/1:1:46 blocked for more than 144 seconds. Not tainted 6.11.0-syzkaller-10622-gaa486552a110 #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/1:1 state:D stack:24304 pid:46 tgid:46 ppid:2 flags:0x00004000 Workqueue: events_power_efficient crda_timeout_work Call Trace: <TASK> context_switch kernel/sched/core.c:5315 [inline] __schedule+0x1895/0x4b30 kernel/sched/core.c:6675 __schedule_loop kernel/sched/core.c:6752 [inline] schedule+0x14b/0x320 kernel/sched/core.c:6767 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6824 __mutex_lock_common kernel/locking/mutex.c:684 [inline] __mutex_lock+0x6a7/0xd70 kernel/locking/mutex.c:752 crda_timeout_work+0x15/0x50 net/wireless/reg.c:540 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Showing all locks held in the system: 3 locks held by kworker/1:0/25: 1 lock held by khungtaskd/30: #0: ffffffff8e937ee0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline] #0: ffffffff8e937ee0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline] #0: ffffffff8e937ee0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6701 --- 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@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. For information about bisection process see: https://goo.gl/tpsmEJ#bisection If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. 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
