Hello, syzbot found the following issue on: HEAD commit: 0913ec336a6c net: ks8851: Fix deadlock with the SPI chip v.. git tree: net console output: https://syzkaller.appspot.com/x/log.txt?x=11fcf3b9980000 kernel config: https://syzkaller.appspot.com/x/.config?x=864caee5f78cab51 dashboard link: https://syzkaller.appspot.com/bug?extid=ea134023eba0b937095a compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/ca08c938c680/disk-0913ec33.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/94b3b925e4c6/vmlinux-0913ec33.xz kernel image: https://storage.googleapis.com/syzbot-assets/ecb897178dbe/bzImage-0913ec33.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+ea134023eba0b937095a@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 1 PID: 1057 at net/ieee802154/core.c:354 cfg802154_pernet_exit+0xb9/0xe0 net/ieee802154/core.c:354 Modules linked in: CPU: 1 PID: 1057 Comm: kworker/u8:5 Not tainted 6.10.0-rc6-syzkaller-00170-g0913ec336a6c #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024 Workqueue: netns cleanup_net RIP: 0010:cfg802154_pernet_exit+0xb9/0xe0 net/ieee802154/core.c:354 Code: 89 d8 48 c1 e8 03 42 80 3c 28 00 74 08 48 89 df e8 1c b7 c3 f6 48 8b 1b 4c 39 e3 74 12 e8 ef 01 5e f6 eb 89 e8 e8 01 5e f6 90 <0f> 0b 90 eb d0 e8 dd 01 5e f6 eb 05 e8 d6 01 5e f6 5b 41 5c 41 5d RSP: 0018:ffffc90004547a88 EFLAGS: 00010293 RAX: ffffffff8b3825c8 RBX: ffff8880231c2008 RCX: ffff88802251bc00 RDX: 0000000000000000 RSI: 00000000ffffffef RDI: 0000000000000000 RBP: 00000000ffffffef R08: ffffffff8b382595 R09: 1ffffffff1ebcdc4 R10: dffffc0000000000 R11: fffffbfff1ebcdc5 R12: ffffffff8f8d05e0 R13: dffffc0000000000 R14: ffff888022dfd640 R15: ffff8880231c2608 FS: 0000000000000000(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ff96115b460 CR3: 000000005cf20000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ops_exit_list net/core/net_namespace.c:173 [inline] cleanup_net+0x802/0xcc0 net/core/net_namespace.c:640 process_one_work kernel/workqueue.c:3248 [inline] process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3329 worker_thread+0x86d/0xd50 kernel/workqueue.c:3409 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> --- 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 report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title 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
