Hello, syzbot found the following issue on: HEAD commit: 92901222f83d Merge tag 'f2fs-for-6-6-rc1' of git://git.ker.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=17c340b8680000 kernel config: https://syzkaller.appspot.com/x/.config?x=3544ee7492950dd3 dashboard link: https://syzkaller.appspot.com/bug?extid=68849d5e4a6e74f32c06 compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13fe378fa80000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11bf6f7ba80000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/7b5db23b3ecc/disk-92901222.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/135d82cfd540/vmlinux-92901222.xz kernel image: https://storage.googleapis.com/syzbot-assets/6e1b0da81493/bzImage-92901222.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+68849d5e4a6e74f32c06@xxxxxxxxxxxxxxxxxxxxxxxxx write to /proc/sys/kernel/softlockup_all_cpu_backtrace failed: No such file or directory BUG: memory leak unreferenced object 0xffff88810f8a4e80 (size 64): comm "kworker/0:1", pid 9, jiffies 4294945857 (age 8.050s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ ff ff ff ff 00 00 00 00 00 00 00 00 30 30 00 00 ............00.. backtrace: [<ffffffff815739f5>] kmalloc_trace+0x25/0x90 mm/slab_common.c:1114 [<ffffffff84739940>] kmalloc include/linux/slab.h:599 [inline] [<ffffffff84739940>] kzalloc include/linux/slab.h:720 [inline] [<ffffffff84739940>] regulatory_hint_core net/wireless/reg.c:3218 [inline] [<ffffffff84739940>] restore_regulatory_settings+0x820/0xa80 net/wireless/reg.c:3552 [<ffffffff84739d71>] crda_timeout_work+0x21/0x30 net/wireless/reg.c:540 [<ffffffff812c8f1d>] process_one_work+0x23d/0x530 kernel/workqueue.c:2630 [<ffffffff812c9ac7>] process_scheduled_works kernel/workqueue.c:2703 [inline] [<ffffffff812c9ac7>] worker_thread+0x327/0x590 kernel/workqueue.c:2784 [<ffffffff812d6f9b>] kthread+0x12b/0x170 kernel/kthread.c:388 [<ffffffff81149875>] ret_from_fork+0x45/0x50 arch/x86/kernel/process.c:147 [<ffffffff81002be1>] ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304 write to /proc/sys/kernel/hung_task_check_interval_secs failed: No such file or directory write to /proc/sys/kernel/softlockup_all_cpu_backtrace failed: No such file or directory write to /proc/sys/kernel/hung_task_check_interval_secs failed: No such file or directory write to /proc/sys/kernel/softlockup_all_cpu_backtrace failed: No such file or directory --- 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. If the bug is already fixed, 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 bug's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the bug is a duplicate of another bug, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup