* Re: [syzbot] [v9fs?] INFO: task hung in v9fs_evict_inode [not found] <20250511001723.1876-1-hdanton@sina.com> @ 2025-05-11 1:28 ` syzbot 0 siblings, 0 replies; 8+ messages in thread From: syzbot @ 2025-05-11 1:28 UTC (permalink / raw) To: hdanton, linux-kernel, syzkaller-bugs Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: INFO: task hung in v9fs_evict_inode INFO: task syz-executor:6613 blocked for more than 143 seconds. Not tainted 6.15.0-rc5-syzkaller-00300-g3ce9925823c7-dirty #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor state:D stack:22232 pid:6613 tgid:6613 ppid:1 task_flags:0x400140 flags:0x00004004 Call Trace: <TASK> context_switch kernel/sched/core.c:5382 [inline] __schedule+0x168f/0x4c70 kernel/sched/core.c:6767 __schedule_loop kernel/sched/core.c:6845 [inline] schedule+0x165/0x360 kernel/sched/core.c:6860 netfs_wait_for_outstanding_io include/linux/netfs.h:558 [inline] v9fs_evict_inode+0x170/0x320 fs/9p/vfs_inode.c:348 evict+0x501/0x9c0 fs/inode.c:810 __dentry_kill+0x209/0x660 fs/dcache.c:660 dput+0x19f/0x2b0 fs/dcache.c:902 shrink_dcache_for_umount+0xa0/0x170 fs/dcache.c:1612 generic_shutdown_super+0x67/0x2c0 fs/super.c:620 kill_anon_super+0x3b/0x70 fs/super.c:1237 v9fs_kill_super+0x4c/0x90 fs/9p/vfs_super.c:193 deactivate_locked_super+0xb9/0x130 fs/super.c:473 cleanup_mnt+0x425/0x4c0 fs/namespace.c:1431 task_work_run+0x1d1/0x260 kernel/task_work.c:227 resume_user_mode_work+0x5e/0x80 include/linux/resume_user_mode.h:50 exit_to_user_mode_loop kernel/entry/common.c:114 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x9a/0x120 kernel/entry/common.c:218 do_syscall_64+0x103/0x210 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fa60458fc97 RSP: 002b:00007fffd9b8ae58 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 RAX: 0000000000000000 RBX: 00007fa60461089d RCX: 00007fa60458fc97 RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fffd9b8af10 RBP: 00007fffd9b8af10 R08: 0000000000000000 R09: 0000000000000000 R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fffd9b8bfa0 R13: 00007fa60461089d R14: 000000000003486c R15: 00007fffd9b8bfe0 </TASK> INFO: task syz-executor:6620 blocked for more than 144 seconds. Not tainted 6.15.0-rc5-syzkaller-00300-g3ce9925823c7-dirty #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor state:D stack:22072 pid:6620 tgid:6620 ppid:1 task_flags:0x400140 flags:0x00004004 Call Trace: <TASK> context_switch kernel/sched/core.c:5382 [inline] __schedule+0x168f/0x4c70 kernel/sched/core.c:6767 __schedule_loop kernel/sched/core.c:6845 [inline] schedule+0x165/0x360 kernel/sched/core.c:6860 netfs_wait_for_outstanding_io include/linux/netfs.h:558 [inline] v9fs_evict_inode+0x170/0x320 fs/9p/vfs_inode.c:348 evict+0x501/0x9c0 fs/inode.c:810 __dentry_kill+0x209/0x660 fs/dcache.c:660 dput+0x19f/0x2b0 fs/dcache.c:902 shrink_dcache_for_umount+0xa0/0x170 fs/dcache.c:1612 generic_shutdown_super+0x67/0x2c0 fs/super.c:620 kill_anon_super+0x3b/0x70 fs/super.c:1237 v9fs_kill_super+0x4c/0x90 fs/9p/vfs_super.c:193 deactivate_locked_super+0xb9/0x130 fs/super.c:473 cleanup_mnt+0x425/0x4c0 fs/namespace.c:1431 task_work_run+0x1d1/0x260 kernel/task_work.c:227 resume_user_mode_work+0x5e/0x80 include/linux/resume_user_mode.h:50 exit_to_user_mode_loop kernel/entry/common.c:114 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x9a/0x120 kernel/entry/common.c:218 do_syscall_64+0x103/0x210 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f1cd6b8fc97 RSP: 002b:00007ffc6ff322e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 RAX: 0000000000000000 RBX: 00007f1cd6c1089d RCX: 00007f1cd6b8fc97 RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffc6ff323a0 RBP: 00007ffc6ff323a0 R08: 0000000000000000 R09: 0000000000000000 R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffc6ff33430 R13: 00007f1cd6c1089d R14: 0000000000034c04 R15: 00007ffc6ff33470 </TASK> Showing all locks held in the system: 3 locks held by kworker/0:0/9: #0: ffff88801a080d48 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3213 [inline] #0: ffff88801a080d48 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x9b1/0x17a0 kernel/workqueue.c:3319 #1: ffffc900000e7c60 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3214 [inline] #1: ffffc900000e7c60 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ec/0x17a0 kernel/workqueue.c:3319 #2: ffff888068497240 (&data->fib_lock){+.+.}-{4:4}, at: nsim_fib_event_work+0x26b/0x3180 drivers/net/netdevsim/fib.c:1490 1 lock held by khungtaskd/31: #0: ffffffff8df3b860 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline] #0: ffffffff8df3b860 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline] #0: ffffffff8df3b860 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6764 3 locks held by kworker/u8:3/54: #0: ffff88803041b148 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3213 [inline] #0: ffff88803041b148 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0x9b1/0x17a0 kernel/workqueue.c:3319 #1: ffffc90000bf7c60 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3214 [inline] #1: ffffc90000bf7c60 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ec/0x17a0 kernel/workqueue.c:3319 #2: ffffffff8f2e27c8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline] #2: ffffffff8f2e27c8 (rtnl_mutex){+.+.}-{4:4}, at: addrconf_dad_work+0x112/0x14b0 net/ipv6/addrconf.c:4198 3 locks held by kworker/u8:4/63: 2 locks held by kworker/u8:5/131: #0: ffff88801a089148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3213 [inline] #0: ffff88801a089148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x9b1/0x17a0 kernel/workqueue.c:3319 #1: ffffc90002e2fc60 ((work_completion)(&rreq->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3214 [inline] #1: ffffc90002e2fc60 ((work_completion)(&rreq->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ec/0x17a0 kernel/workqueue.c:3319 2 locks held by kworker/u8:6/1079: #0: ffff88801a089148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3213 [inline] #0: ffff88801a089148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x9b1/0x17a0 kernel/workqueue.c:3319 #1: ffffc90003807c60 ((work_completion)(&rreq->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3214 [inline] #1: ffffc90003807c60 ((work_completion)(&rreq->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ec/0x17a0 kernel/workqueue.c:3319 2 locks held by kworker/u8:9/3002: #0: ffff88801a089148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3213 [inline] #0: ffff88801a089148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x9b1/0x17a0 kernel/workqueue.c:3319 #1: ffffc9000baffc60 ((work_completion)(&rreq->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3214 [inline] #1: ffffc9000baffc60 ((work_completion)(&rreq->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ec/0x17a0 kernel/workqueue.c:3319 1 lock held by klogd/5180: 2 locks held by getty/5580: #0: ffff888030f7e0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243 #1: ffffc900036cb2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222 1 lock held by syz-executor/6613: #0: ffff88802ca5e0e0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock fs/super.c:56 [inline] #0: ffff88802ca5e0e0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline] #0: ffff88802ca5e0e0 (&type->s_umount_key#54){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505 1 lock held by syz-executor/6620: #0: ffff88807cd440e0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock fs/super.c:56 [inline] #0: ffff88807cd440e0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline] #0: ffff88807cd440e0 (&type->s_umount_key#54){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505 1 lock held by syz-executor/12720: #0: ffff8880687d40e0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock fs/super.c:56 [inline] #0: ffff8880687d40e0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline] #0: ffff8880687d40e0 (&type->s_umount_key#54){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505 1 lock held by syz-executor/13177: #0: ffffffff8df41200 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x4c/0x570 kernel/rcu/tree.c:3774 1 lock held by syz-executor/13628: #0: ffffffff8df41200 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x4c/0x570 kernel/rcu/tree.c:3774 1 lock held by syz-executor/18686: #0: ffffffff8df41200 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x4c/0x570 kernel/rcu/tree.c:3774 3 locks held by syz-executor/19117: #0: ffffffff8f2e27c8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline] #0: ffffffff8f2e27c8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_nets_lock net/core/rtnetlink.c:341 [inline] #0: ffffffff8f2e27c8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x8db/0x1c70 net/core/rtnetlink.c:4064 #1: ffff88805dc594e8 (&wg->device_update_lock){+.+.}-{4:4}, at: wg_open+0x227/0x420 drivers/net/wireguard/device.c:50 #2: ffffffff8df41338 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:304 [inline] #2: ffffffff8df41338 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x2f4/0x730 kernel/rcu/tree_exp.h:998 2 locks held by dhcpcd/19459: #0: ffff888061b2c258 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1651 [inline] #0: ffff888061b2c258 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x32/0xcd0 net/packet/af_packet.c:3252 #1: ffffffff8df41338 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:336 [inline] #1: ffffffff8df41338 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x3b7/0x730 kernel/rcu/tree_exp.h:998 ============================================= NMI backtrace for cpu 1 CPU: 1 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.15.0-rc5-syzkaller-00300-g3ce9925823c7-dirty #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 nmi_cpu_backtrace+0x39e/0x3d0 lib/nmi_backtrace.c:113 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62 trigger_all_cpu_backtrace include/linux/nmi.h:158 [inline] check_hung_uninterruptible_tasks kernel/hung_task.c:274 [inline] watchdog+0xfee/0x1030 kernel/hung_task.c:437 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK> Sending NMI from CPU 1 to CPUs 0: NMI backtrace for cpu 0 CPU: 0 UID: 0 PID: 19463 Comm: syz.4.5724 Not tainted 6.15.0-rc5-syzkaller-00300-g3ce9925823c7-dirty #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 RIP: 0010:unwind_next_frame+0xc93/0x2390 arch/x86/kernel/unwind_orc.c:592 Code: 80 3c 28 00 48 8b 5c 24 70 4c 8b 6c 24 50 4c 8b 64 24 10 74 08 48 89 df e8 8a e9 ad 00 4c 89 23 ba 10 00 00 00 4c 89 ef 31 f6 <e8> 58 eb ad 00 48 8b 14 24 e9 c5 04 00 00 4c 89 7c 24 28 48 89 5c RSP: 0018:ffffc90005206b58 EFLAGS: 00000046 RAX: 1ffff92000a40d98 RBX: ffffc90005206cc0 RCX: 1ffff92000a40d01 RDX: 0000000000000010 RSI: 0000000000000000 RDI: ffffc90005206cd8 RBP: dffffc0000000000 R08: 0000000000000009 R09: 0000000000080000 R10: 0000000000000000 R11: ffffffff8171a9f5 R12: ffffc90005206c88 R13: ffffc90005206cd8 R14: ffffc90005206c88 R15: ffffc90005206cd0 FS: 000055556d1b9500(0000) GS:ffff888126100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000c006aae000 CR3: 00000000709c2000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> __unwind_start+0x5b9/0x760 arch/x86/kernel/unwind_orc.c:758 unwind_start arch/x86/include/asm/unwind.h:64 [inline] arch_stack_walk+0xe4/0x150 arch/x86/kernel/stacktrace.c:24 stack_trace_save+0x9c/0xe0 kernel/stacktrace.c:122 kasan_save_stack+0x3e/0x60 mm/kasan/common.c:47 kasan_record_aux_stack+0xbc/0xd0 mm/kasan/generic.c:548 insert_work+0x3d/0x330 kernel/workqueue.c:2183 __queue_work+0xcfc/0xfe0 kernel/workqueue.c:2341 queue_work_on+0x181/0x270 kernel/workqueue.c:2392 queue_work include/linux/workqueue.h:662 [inline] schedule_work include/linux/workqueue.h:723 [inline] p9_fd_request+0x2a8/0x4c0 net/9p/trans_fd.c:695 p9_client_rpc+0x2da/0xa70 net/9p/client.c:706 p9_client_write+0x33b/0x740 net/9p/client.c:1648 v9fs_issue_write+0xdd/0x180 fs/9p/vfs_addr.c:59 netfs_do_issue_write fs/netfs/write_issue.c:239 [inline] netfs_issue_write fs/netfs/write_issue.c:269 [inline] netfs_advance_write+0x4c1/0xc30 fs/netfs/write_issue.c:310 netfs_write_folio+0x11cb/0x1bb0 fs/netfs/write_issue.c:498 netfs_writepages+0x700/0x8e0 fs/netfs/write_issue.c:594 do_writepages+0x3ae/0x7b0 mm/page-writeback.c:2656 filemap_fdatawrite_wbc mm/filemap.c:386 [inline] __filemap_fdatawrite_range mm/filemap.c:419 [inline] __filemap_fdatawrite mm/filemap.c:425 [inline] filemap_fdatawrite+0x191/0x230 mm/filemap.c:430 v9fs_dir_release+0x15d/0x510 fs/9p/vfs_dir.c:219 __fput+0x449/0xa70 fs/file_table.c:465 task_work_run+0x1d1/0x260 kernel/task_work.c:227 resume_user_mode_work+0x5e/0x80 include/linux/resume_user_mode.h:50 exit_to_user_mode_loop kernel/entry/common.c:114 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x9a/0x120 kernel/entry/common.c:218 do_syscall_64+0x103/0x210 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fedd5b8e969 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffebd6c8048 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4 RAX: 0000000000000000 RBX: 0000000000058570 RCX: 00007fedd5b8e969 RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003 RBP: 00007fedd5db7ba0 R08: 0000000000000001 R09: 0000000abd6c833f R10: 00007fedd5a00000 R11: 0000000000000246 R12: 00007fedd5db5fac R13: 00007fedd5db5fa0 R14: ffffffffffffffff R15: 00007ffebd6c8160 </TASK> Tested on: commit: 3ce99258 Merge tag 'mm-hotfixes-stable-2025-05-10-14-2.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=11cad768580000 kernel config: https://syzkaller.appspot.com/x/.config?x=b9683d529ec1b880 dashboard link: https://syzkaller.appspot.com/bug?extid=56bd5818697f0f93fdd9 compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2 patch: https://syzkaller.appspot.com/x/patch.diff?x=124cccf4580000 ^ permalink raw reply [flat|nested] 8+ messages in thread
* [syzbot] [v9fs?] INFO: task hung in v9fs_evict_inode
@ 2024-12-05 10:28 syzbot
2025-05-10 17:00 ` syzbot
2025-11-18 2:14 ` syzbot
0 siblings, 2 replies; 8+ messages in thread
From: syzbot @ 2024-12-05 10:28 UTC (permalink / raw)
To: asmadeus, ericvh, linux-kernel, linux_oss, lucho, syzkaller-bugs,
v9fs
Hello,
syzbot found the following issue on:
HEAD commit: f486c8aa16b8 Add linux-next specific files for 20241128
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=159927c0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e348a4873516af92
dashboard link: https://syzkaller.appspot.com/bug?extid=56bd5818697f0f93fdd9
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=12c765e8580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/beb58ebb63cf/disk-f486c8aa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b241b5609e64/vmlinux-f486c8aa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c9d817f665f2/bzImage-f486c8aa.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+56bd5818697f0f93fdd9@syzkaller.appspotmail.com
INFO: task syz-executor:5928 blocked for more than 143 seconds.
Not tainted 6.12.0-next-20241128-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:20080 pid:5928 tgid:5928 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5369 [inline]
__schedule+0x1850/0x4c30 kernel/sched/core.c:6756
__schedule_loop kernel/sched/core.c:6833 [inline]
schedule+0x14b/0x320 kernel/sched/core.c:6848
netfs_wait_for_outstanding_io include/linux/netfs.h:558 [inline]
v9fs_evict_inode+0x171/0x360 fs/9p/vfs_inode.c:348
evict+0x4e8/0x9a0 fs/inode.c:796
__dentry_kill+0x20d/0x630 fs/dcache.c:625
dput+0x19f/0x2b0 fs/dcache.c:867
shrink_dcache_for_umount+0xb4/0x180 fs/dcache.c:1577
generic_shutdown_super+0x6a/0x2d0 fs/super.c:620
kill_anon_super+0x3b/0x70 fs/super.c:1237
v9fs_kill_super+0x4c/0x90 fs/9p/vfs_super.c:193
deactivate_locked_super+0xc4/0x130 fs/super.c:473
cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373
task_work_run+0x24f/0x310 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x13f/0x340 kernel/entry/common.c:218
do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f8a37781b77
RSP: 002b:00007ffe40eae1a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f8a37781b77
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffe40eae260
RBP: 00007ffe40eae260 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffe40eaf2e0
R13: 00007f8a377f3824 R14: 000000000003f13f R15: 00007ffe40eaf320
</TASK>
Showing all locks held in the system:
3 locks held by kworker/u8:1/12:
1 lock held by khungtaskd/30:
#0: ffffffff8e937b20 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
#0: ffffffff8e937b20 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
#0: ffffffff8e937b20 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6744
2 locks held by kworker/u8:8/3481:
#0: ffff88801ac89148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3204 [inline]
#0: ffff88801ac89148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x93b/0x1840 kernel/workqueue.c:3310
#1: ffffc9000cdb7d00 ((work_completion)(&rreq->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3205 [inline]
#1: ffffc9000cdb7d00 ((work_completion)(&rreq->work)){+.+.}-{0:0}, at: process_scheduled_works+0x976/0x1840 kernel/workqueue.c:3310
2 locks held by getty/5584:
#0: ffff88814e3000a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc900032eb2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x6a6/0x1e00 drivers/tty/n_tty.c:2211
1 lock held by syz-executor/5928:
#0: ffff8880352ee0e0 (&type->s_umount_key#51){+.+.}-{4:4}, at: __super_lock fs/super.c:56 [inline]
#0: ffff8880352ee0e0 (&type->s_umount_key#51){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff8880352ee0e0 (&type->s_umount_key#51){+.+.}-{4:4}, at: deactivate_super+0xb5/0xf0 fs/super.c:505
1 lock held by syz.5.407/7698:
1 lock held by syz.3.408/7704:
1 lock held by syz.4.409/7705:
1 lock held by syz.0.410/7711:
1 lock held by syz.2.411/7714:
=============================================
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 30 Comm: khungtaskd Not tainted 6.12.0-next-20241128-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
nmi_cpu_backtrace+0x49c/0x4d0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x198/0x320 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:162 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:234 [inline]
watchdog+0xff6/0x1040 kernel/hung_task.c:397
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>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 7698 Comm: syz.5.407 Not tainted 6.12.0-next-20241128-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:check_preemption_disabled+0x2/0x120 lib/smp_processor_id.c:13
Code: 8d 5f 8c 48 c7 c6 80 8d 5f 8c eb 1c 66 2e 0f 1f 84 00 00 00 00 00 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 41 57 <41> 56 41 54 53 48 83 ec 10 65 48 8b 04 25 28 00 00 00 48 89 44 24
RSP: 0018:ffffc9000478ee90 EFLAGS: 00000283
RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffffffff817aaec4
RDX: 0000000000000000 RSI: ffffffff8c5f8d80 RDI: ffffffff8c5f8d40
RBP: ffffc9000478f008 R08: ffffffff90199eb7 R09: 1ffffffff20333d6
R10: dffffc0000000000 R11: fffffbfff20333d7 R12: 1ffff920008f1de0
R13: dffffc0000000000 R14: 0000000000000000 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f71caed9d58 CR3: 0000000065d88000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
rcu_is_watching_curr_cpu include/linux/context_tracking.h:128 [inline]
rcu_is_watching+0x15/0xb0 kernel/rcu/tree.c:737
trace_lock_acquire include/trace/events/lock.h:24 [inline]
lock_acquire+0xe3/0x550 kernel/locking/lockdep.c:5820
rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
rcu_read_lock include/linux/rcupdate.h:849 [inline]
page_ext_get+0x3d/0x2a0 mm/page_ext.c:525
__page_table_check_zero+0xb1/0x350 mm/page_table_check.c:148
page_table_check_free include/linux/page_table_check.h:41 [inline]
free_pages_prepare mm/page_alloc.c:1128 [inline]
free_unref_folios+0xf76/0x1a90 mm/page_alloc.c:2740
folios_put_refs+0x76c/0x860 mm/swap.c:962
folio_batch_release include/linux/pagevec.h:101 [inline]
shmem_undo_range+0x64c/0x1cf0 mm/shmem.c:1040
shmem_truncate_range mm/shmem.c:1152 [inline]
shmem_evict_inode+0x29b/0xa80 mm/shmem.c:1280
evict+0x4e8/0x9a0 fs/inode.c:796
__dentry_kill+0x20d/0x630 fs/dcache.c:625
dput+0x19f/0x2b0 fs/dcache.c:867
__fput+0x5ba/0xa50 fs/file_table.c:458
task_work_run+0x24f/0x310 kernel/task_work.c:239
exit_task_work include/linux/task_work.h:43 [inline]
do_exit+0xa2f/0x28e0 kernel/exit.c:938
do_group_exit+0x207/0x2c0 kernel/exit.c:1087
get_signal+0x16b2/0x1750 kernel/signal.c:3016
arch_do_signal_or_restart+0x96/0x860 arch/x86/kernel/signal.c:337
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0xce/0x340 kernel/entry/common.c:218
do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fefa3180849
Code: Unable to access opcode bytes at 0x7fefa318081f.
RSP: 002b:00007fefa3eb0058 EFLAGS: 00000246 ORIG_RAX: 000000000000012b
RAX: 0000000000010106 RBX: 00007fefa3346080 RCX: 00007fefa3180849
RDX: 0000000000010106 RSI: 00000000200000c0 RDI: 0000000000000008
RBP: 00007fefa31f3986 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fefa3346080 R15: 00007ffc05aa9138
</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@googlegroups.com.
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 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
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [syzbot] [v9fs?] INFO: task hung in v9fs_evict_inode 2024-12-05 10:28 syzbot @ 2025-05-10 17:00 ` syzbot 2025-11-18 2:14 ` syzbot 1 sibling, 0 replies; 8+ messages in thread From: syzbot @ 2025-05-10 17:00 UTC (permalink / raw) To: asmadeus, ericvh, linux-kernel, linux_oss, lucho, syzkaller-bugs, v9fs syzbot has found a reproducer for the following issue on: HEAD commit: 0e1329d4045c Merge tag 'rust-fixes-6.15-2' of git://git.ke.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15a76cf4580000 kernel config: https://syzkaller.appspot.com/x/.config?x=b9683d529ec1b880 dashboard link: https://syzkaller.appspot.com/bug?extid=56bd5818697f0f93fdd9 compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=123d34d4580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d91670580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/ab812a79f364/disk-0e1329d4.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/3f8097de4dd6/vmlinux-0e1329d4.xz kernel image: https://storage.googleapis.com/syzbot-assets/58fe086be90f/bzImage-0e1329d4.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+56bd5818697f0f93fdd9@syzkaller.appspotmail.com INFO: task syz-executor256:5823 blocked for more than 143 seconds. Not tainted 6.15.0-rc5-syzkaller-00204-g0e1329d4045c #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor256 state:D stack:25112 pid:5823 tgid:5823 ppid:5816 task_flags:0x400140 flags:0x00004002 Call Trace: <TASK> context_switch kernel/sched/core.c:5382 [inline] __schedule+0x168f/0x4c70 kernel/sched/core.c:6767 __schedule_loop kernel/sched/core.c:6845 [inline] schedule+0x165/0x360 kernel/sched/core.c:6860 netfs_wait_for_outstanding_io include/linux/netfs.h:558 [inline] v9fs_evict_inode+0x170/0x320 fs/9p/vfs_inode.c:348 evict+0x501/0x9c0 fs/inode.c:810 __dentry_kill+0x209/0x660 fs/dcache.c:660 dput+0x19f/0x2b0 fs/dcache.c:902 shrink_dcache_for_umount+0xa0/0x170 fs/dcache.c:1612 generic_shutdown_super+0x67/0x2c0 fs/super.c:620 kill_anon_super+0x3b/0x70 fs/super.c:1237 v9fs_kill_super+0x4c/0x90 fs/9p/vfs_super.c:193 deactivate_locked_super+0xb9/0x130 fs/super.c:473 cleanup_mnt+0x425/0x4c0 fs/namespace.c:1435 task_work_run+0x1d1/0x260 kernel/task_work.c:227 resume_user_mode_work+0x5e/0x80 include/linux/resume_user_mode.h:50 exit_to_user_mode_loop kernel/entry/common.c:114 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x9a/0x120 kernel/entry/common.c:218 do_syscall_64+0x103/0x210 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f938ec869b7 RSP: 002b:00007ffcc34c98a8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a6 RAX: 0000000000000000 RBX: 000000000001a18b RCX: 00007f938ec869b7 RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffcc34c9960 RBP: 00007ffcc34c9960 R08: 0000000000000000 R09: 0000000000000000 R10: 00000000ffffffff R11: 0000000000000202 R12: 00007ffcc34ca9d0 R13: 000055556f5f06c0 R14: 00007ffcc34ca9d0 R15: 00000000000000a9 </TASK> Showing all locks held in the system: 1 lock held by khungtaskd/31: #0: ffffffff8df3b860 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline] #0: ffffffff8df3b860 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline] #0: ffffffff8df3b860 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6764 2 locks held by kworker/u8:6/1320: #0: ffff88801a089148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3213 [inline] #0: ffff88801a089148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x9b1/0x17a0 kernel/workqueue.c:3319 #1: ffffc900045cfc60 ((work_completion)(&rreq->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3214 [inline] #1: ffffc900045cfc60 ((work_completion)(&rreq->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ec/0x17a0 kernel/workqueue.c:3319 2 locks held by kworker/u8:10/3558: #0: ffff88801a089148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3213 [inline] #0: ffff88801a089148 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x9b1/0x17a0 kernel/workqueue.c:3319 #1: ffffc9000c4e7c60 ((work_completion)(&rreq->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3214 [inline] #1: ffffc9000c4e7c60 ((work_completion)(&rreq->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ec/0x17a0 kernel/workqueue.c:3319 2 locks held by getty/5579: #0: ffff888030a8b0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243 #1: ffffc90002ffe2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222 1 lock held by syz-executor256/5819: #0: ffffffff8df41200 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x4c/0x570 kernel/rcu/tree.c:3774 1 lock held by syz-executor256/5821: #0: ffffffff8df41338 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:336 [inline] #0: ffffffff8df41338 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x3b7/0x730 kernel/rcu/tree_exp.h:998 1 lock held by syz-executor256/5822: #0: ffff888077f8e0e0 (&type->s_umount_key#43){+.+.}-{4:4}, at: __super_lock fs/super.c:56 [inline] #0: ffff888077f8e0e0 (&type->s_umount_key#43){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline] #0: ffff888077f8e0e0 (&type->s_umount_key#43){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505 1 lock held by syz-executor256/5823: #0: ffff88807f15a0e0 (&type->s_umount_key#43){+.+.}-{4:4}, at: __super_lock fs/super.c:56 [inline] #0: ffff88807f15a0e0 (&type->s_umount_key#43){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline] #0: ffff88807f15a0e0 (&type->s_umount_key#43){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:505 1 lock held by syz-executor256/11897: #0: ffffffff8df41338 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:304 [inline] #0: ffffffff8df41338 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x2f4/0x730 kernel/rcu/tree_exp.h:998 ============================================= NMI backtrace for cpu 0 CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.15.0-rc5-syzkaller-00204-g0e1329d4045c #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: <TASK> dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 nmi_cpu_backtrace+0x39e/0x3d0 lib/nmi_backtrace.c:113 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62 trigger_all_cpu_backtrace include/linux/nmi.h:158 [inline] check_hung_uninterruptible_tasks kernel/hung_task.c:274 [inline] watchdog+0xfee/0x1030 kernel/hung_task.c:437 kthread+0x70e/0x8a0 kernel/kthread.c:464 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK> Sending NMI from CPU 0 to CPUs 1: NMI backtrace for cpu 1 CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.15.0-rc5-syzkaller-00204-g0e1329d4045c #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 RIP: 0010:pv_native_safe_halt+0x13/0x20 arch/x86/kernel/paravirt.c:81 Code: cc cc cc cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 0f 00 2d 03 1b 19 00 f3 0f 1e fa fb f4 <c3> cc cc cc cc cc cc cc cc cc cc cc cc 90 90 90 90 90 90 90 90 90 RSP: 0018:ffffc90000197de0 EFLAGS: 000002c6 RAX: aeb744c0f33a6400 RBX: ffffffff81974e28 RCX: aeb744c0f33a6400 RDX: 0000000000000001 RSI: ffffffff8d7372f8 RDI: ffffffff8bc0fee0 RBP: ffffc90000197f20 R08: ffff8880b8932b5b R09: 1ffff1101712656b R10: dffffc0000000000 R11: ffffed101712656c R12: ffffffff8f7da770 R13: 0000000000000001 R14: 0000000000000001 R15: 1ffff110038d9b40 FS: 0000000000000000(0000) GS:ffff888126200000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055556f5f86f8 CR3: 0000000078712000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> arch_safe_halt arch/x86/include/asm/paravirt.h:107 [inline] default_idle+0x13/0x20 arch/x86/kernel/process.c:748 default_idle_call+0x74/0xb0 kernel/sched/idle.c:117 cpuidle_idle_call kernel/sched/idle.c:185 [inline] do_idle+0x1e8/0x510 kernel/sched/idle.c:325 cpu_startup_entry+0x44/0x60 kernel/sched/idle.c:423 start_secondary+0x101/0x110 arch/x86/kernel/smpboot.c:315 common_startup_64+0x13e/0x147 </TASK> --- 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. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [v9fs?] INFO: task hung in v9fs_evict_inode 2024-12-05 10:28 syzbot 2025-05-10 17:00 ` syzbot @ 2025-11-18 2:14 ` syzbot 2025-11-18 15:25 ` David Howells 2025-11-18 16:30 ` David Howells 1 sibling, 2 replies; 8+ messages in thread From: syzbot @ 2025-11-18 2:14 UTC (permalink / raw) To: asmadeus, brauner, dhowells, ericvh, hdanton, linux-kernel, linux_oss, lucho, max.kellermann, syzkaller-bugs, v9fs syzbot suspects this issue was fixed by commit: commit 4d428dca252c858bfac691c31fa95d26cd008706 Author: Max Kellermann <max.kellermann@ionos.com> Date: Thu Sep 25 13:08:20 2025 +0000 netfs: fix reference leak bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1478fb42580000 start commit: 4871b7cb27f4 Merge tag 'v6.16-rc6-smb3-client-fixes' of gi.. git tree: upstream kernel config: https://syzkaller.appspot.com/x/.config?x=12b5044868deb866 dashboard link: https://syzkaller.appspot.com/bug?extid=56bd5818697f0f93fdd9 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14d7e38c580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=132ff8f0580000 If the result looks correct, please mark the issue as fixed by replying with: #syz fix: netfs: fix reference leak For information about bisection process see: https://goo.gl/tpsmEJ#bisection ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [v9fs?] INFO: task hung in v9fs_evict_inode 2025-11-18 2:14 ` syzbot @ 2025-11-18 15:25 ` David Howells 2025-11-18 16:12 ` Max Kellermann 2025-11-18 16:30 ` David Howells 1 sibling, 1 reply; 8+ messages in thread From: David Howells @ 2025-11-18 15:25 UTC (permalink / raw) To: syzbot, max.kellermann Cc: dhowells, asmadeus, brauner, ericvh, hdanton, linux-kernel, linux_oss, lucho, syzkaller-bugs, v9fs syzbot <syzbot+56bd5818697f0f93fdd9@syzkaller.appspotmail.com> wrote: > syzbot suspects this issue was fixed by commit: > > commit 4d428dca252c858bfac691c31fa95d26cd008706 > Author: Max Kellermann <max.kellermann@ionos.com> > Date: Thu Sep 25 13:08:20 2025 +0000 > > netfs: fix reference leak > ... > dashboard link: https://syzkaller.appspot.com/bug?extid=56bd5818697f0f93fdd9 That sounds reasonable. I don't know if Max has a blocked cpu message for comparison? David ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [v9fs?] INFO: task hung in v9fs_evict_inode 2025-11-18 15:25 ` David Howells @ 2025-11-18 16:12 ` Max Kellermann 2025-11-18 16:30 ` David Howells 0 siblings, 1 reply; 8+ messages in thread From: Max Kellermann @ 2025-11-18 16:12 UTC (permalink / raw) To: David Howells Cc: syzbot, asmadeus, brauner, ericvh, hdanton, linux-kernel, linux_oss, lucho, syzkaller-bugs, v9fs On Tue, Nov 18, 2025 at 4:25 PM David Howells <dhowells@redhat.com> wrote: > > syzbot <syzbot+56bd5818697f0f93fdd9@syzkaller.appspotmail.com> wrote: > > > syzbot suspects this issue was fixed by commit: > > > > commit 4d428dca252c858bfac691c31fa95d26cd008706 > > Author: Max Kellermann <max.kellermann@ionos.com> > > Date: Thu Sep 25 13:08:20 2025 +0000 > > > > netfs: fix reference leak > > ... > > dashboard link: https://syzkaller.appspot.com/bug?extid=56bd5818697f0f93fdd9 > > That sounds reasonable. I don't know if Max has a blocked cpu message for > comparison? Indeed, that's the same symptom I had; my patch is the fix. Unfortunately, I don't keep any of the debugging output - I should have added that to the patch description. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [v9fs?] INFO: task hung in v9fs_evict_inode 2025-11-18 16:12 ` Max Kellermann @ 2025-11-18 16:30 ` David Howells 0 siblings, 0 replies; 8+ messages in thread From: David Howells @ 2025-11-18 16:30 UTC (permalink / raw) To: Max Kellermann Cc: dhowells, syzbot, asmadeus, brauner, ericvh, hdanton, linux-kernel, linux_oss, lucho, syzkaller-bugs, v9fs Max Kellermann <max.kellermann@ionos.com> wrote: > Indeed, that's the same symptom I had; my patch is the fix. Thanks :-) David ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [syzbot] [v9fs?] INFO: task hung in v9fs_evict_inode 2025-11-18 2:14 ` syzbot 2025-11-18 15:25 ` David Howells @ 2025-11-18 16:30 ` David Howells 1 sibling, 0 replies; 8+ messages in thread From: David Howells @ 2025-11-18 16:30 UTC (permalink / raw) To: syzbot Cc: dhowells, asmadeus, brauner, ericvh, hdanton, linux-kernel, linux_oss, lucho, max.kellermann, syzkaller-bugs, v9fs #syz fix: netfs: fix reference leak ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2025-11-18 16:31 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20250511001723.1876-1-hdanton@sina.com>
2025-05-11 1:28 ` [syzbot] [v9fs?] INFO: task hung in v9fs_evict_inode syzbot
2024-12-05 10:28 syzbot
2025-05-10 17:00 ` syzbot
2025-11-18 2:14 ` syzbot
2025-11-18 15:25 ` David Howells
2025-11-18 16:12 ` Max Kellermann
2025-11-18 16:30 ` David Howells
2025-11-18 16:30 ` David Howells
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox