[<prev] [next>] [day] [month] [year] [list]
Message-ID: <6840cb56.a00a0220.d4325.000f.GAE@google.com>
Date: Wed, 04 Jun 2025 15:40:22 -0700
From: syzbot <syzbot+b10aefdd9ef275e9368d@...kaller.appspotmail.com>
To: asmadeus@...ewreck.org, ericvh@...nel.org, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org, linux_oss@...debyte.com, lucho@...kov.net,
syzkaller-bugs@...glegroups.com, v9fs@...ts.linux.dev
Subject: [syzbot] [v9fs?] [ext4?] INFO: task hung in __iterate_supers
Hello,
syzbot found the following issue on:
HEAD commit: 3a83b350b5be Add linux-next specific files for 20250530
git tree: linux-next
console+strace: https://syzkaller.appspot.com/x/log.txt?x=127da00c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=28859360c84ac63d
dashboard link: https://syzkaller.appspot.com/bug?extid=b10aefdd9ef275e9368d
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13765970580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12f4b00c580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e18e458d13c9/disk-3a83b350.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a1c40854811c/vmlinux-3a83b350.xz
kernel image: https://storage.googleapis.com/syzbot-assets/571f670b130a/bzImage-3a83b350.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f51e108aa24a/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=15765970580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b10aefdd9ef275e9368d@...kaller.appspotmail.com
INFO: task syz-executor419:5916 blocked for more than 143 seconds.
Not tainted 6.15.0-next-20250530-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor419 state:D stack:29576 pid:5916 tgid:5890 ppid:5883 task_flags:0x400040 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5396 [inline]
__schedule+0x16f5/0x4d00 kernel/sched/core.c:6785
__schedule_loop kernel/sched/core.c:6863 [inline]
schedule+0x165/0x360 kernel/sched/core.c:6878
super_lock+0x1c8/0x3b0 fs/super.c:115
__iterate_supers+0x126/0x250 fs/super.c:923
ksys_sync+0x94/0x150 fs/sync.c:102
__ia32_sys_sync+0xe/0x20 fs/sync.c:113
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f90546eea09
RSP: 002b:00007f9054678218 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007f90547706f8 RCX: 00007f90546eea09
RDX: 00007f90546c5526 RSI: 0000000000000000 RDI: 00007f9054678fb0
RBP: 00007f90547706f0 R08: 00007ffc16b879e7 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f905473ca1c
R13: 000000000000006e R14: 0000200000000040 R15: 00007ffc16b879e8
</TASK>
INFO: task syz-executor419:5913 blocked for more than 144 seconds.
Not tainted 6.15.0-next-20250530-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor419 state:D stack:28584 pid:5913 tgid:5891 ppid:5881 task_flags:0x400040 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5396 [inline]
__schedule+0x16f5/0x4d00 kernel/sched/core.c:6785
__schedule_loop kernel/sched/core.c:6863 [inline]
schedule+0x165/0x360 kernel/sched/core.c:6878
super_lock+0x1c8/0x3b0 fs/super.c:115
__iterate_supers+0x126/0x250 fs/super.c:923
ksys_sync+0x94/0x150 fs/sync.c:102
__ia32_sys_sync+0xe/0x20 fs/sync.c:113
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f90546eea09
RSP: 002b:00007f9054678218 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007f90547706f8 RCX: 00007f90546eea09
RDX: 00007f90546c5526 RSI: 0000000000000000 RDI: 00007f9054678fb0
RBP: 00007f90547706f0 R08: 00007ffc16b879e7 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f905473ca1c
R13: 000000000000006e R14: 0000200000000040 R15: 00007ffc16b879e8
</TASK>
INFO: task syz-executor419:5914 blocked for more than 144 seconds.
Not tainted 6.15.0-next-20250530-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor419 state:D stack:29544 pid:5914 tgid:5892 ppid:5882 task_flags:0x400040 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5396 [inline]
__schedule+0x16f5/0x4d00 kernel/sched/core.c:6785
__schedule_loop kernel/sched/core.c:6863 [inline]
schedule+0x165/0x360 kernel/sched/core.c:6878
super_lock+0x1c8/0x3b0 fs/super.c:115
__iterate_supers+0x126/0x250 fs/super.c:923
ksys_sync+0x94/0x150 fs/sync.c:102
__ia32_sys_sync+0xe/0x20 fs/sync.c:113
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f90546eea09
RSP: 002b:00007f9054678218 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007f90547706f8 RCX: 00007f90546eea09
RDX: 00007f90546c5526 RSI: 0000000000000000 RDI: 00007f9054678fb0
RBP: 00007f90547706f0 R08: 00007ffc16b879e7 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f905473ca1c
R13: 000000000000006e R14: 0000200000000040 R15: 00007ffc16b879e8
</TASK>
INFO: task syz-executor419:5915 blocked for more than 145 seconds.
Not tainted 6.15.0-next-20250530-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor419 state:D stack:29576 pid:5915 tgid:5893 ppid:5880 task_flags:0x400040 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5396 [inline]
__schedule+0x16f5/0x4d00 kernel/sched/core.c:6785
__schedule_loop kernel/sched/core.c:6863 [inline]
schedule+0x165/0x360 kernel/sched/core.c:6878
super_lock+0x1c8/0x3b0 fs/super.c:115
__iterate_supers+0x126/0x250 fs/super.c:923
ksys_sync+0x94/0x150 fs/sync.c:102
__ia32_sys_sync+0xe/0x20 fs/sync.c:113
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f90546eea09
RSP: 002b:00007f9054678218 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007f90547706f8 RCX: 00007f90546eea09
RDX: 00007f90546c5526 RSI: 0000000000000000 RDI: 00007f9054678fb0
RBP: 00007f90547706f0 R08: 00007ffc16b879e7 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f905473ca1c
R13: 000000000000006e R14: 0000200000000040 R15: 00007ffc16b879e8
</TASK>
INFO: task syz-executor419:5917 blocked for more than 145 seconds.
Not tainted 6.15.0-next-20250530-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor419 state:D stack:29576 pid:5917 tgid:5895 ppid:5879 task_flags:0x400040 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5396 [inline]
__schedule+0x16f5/0x4d00 kernel/sched/core.c:6785
__schedule_loop kernel/sched/core.c:6863 [inline]
schedule+0x165/0x360 kernel/sched/core.c:6878
super_lock+0x1c8/0x3b0 fs/super.c:115
__iterate_supers+0x126/0x250 fs/super.c:923
ksys_sync+0x94/0x150 fs/sync.c:102
__ia32_sys_sync+0xe/0x20 fs/sync.c:113
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f90546eea09
RSP: 002b:00007f9054678218 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007f90547706f8 RCX: 00007f90546eea09
RDX: 00007f90546eea09 RSI: 0000000000000000 RDI: 0000000000000080
RBP: 00007f90547706f0 R08: 0000000000000000 R09: 0000000000000000
R10: 00007ffc16b879e7 R11: 0000000000000246 R12: 00007f905473ca1c
R13: 000000000000006e R14: 0000200000000040 R15: 00007ffc16b879e8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/31:
#0: ffffffff8e13f140 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
#0: ffffffff8e13f140 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
#0: ffffffff8e13f140 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6770
2 locks held by getty/5595:
#0: ffff888034dd90a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000332b2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
1 lock held by syz-executor419/5894:
1 lock held by syz-executor419/5897:
1 lock held by syz-executor419/5896:
1 lock held by syz-executor419/5898:
1 lock held by syz-executor419/5900:
=============================================
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.15.0-next-20250530-syzkaller #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:307 [inline]
watchdog+0xfee/0x1030 kernel/hung_task.c:470
kthread+0x70e/0x8a0 kernel/kthread.c:464
ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
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: 5900 Comm: syz-executor419 Not tainted 6.15.0-next-20250530-syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:its_return_thunk+0x0/0x10 arch/x86/lib/retpoline.S:412
Code: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc <c3> cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 e9 8b 84 ca f5 cc
RSP: 0018:ffffc9000469fa38 EFLAGS: 00000293
RAX: ffffffff81ad3201 RBX: ffffc9000469fb20 RCX: ffff88807fc99e00
RDX: 0000000000000000 RSI: 746e756f6d65723d RDI: 000000003b9ac9ff
RBP: ffffc9000469faf0 R08: ffffffff8fa127f7 R09: 1ffffffff1f424fe
R10: dffffc0000000000 R11: fffffbfff1f424ff R12: ffffc9000469fa80
R13: ffffffffc4653600 R14: 195d9dfa908f7e3d R15: 73726f73f98510d7
FS: 00007f90546996c0(0000) GS:ffff888125d53000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005606f52b3168 CR3: 0000000077c1a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
set_normalized_timespec64+0xc1/0x1a0 kernel/time/time.c:497
inode_set_ctime_to_ts+0x126/0x2f0 fs/inode.c:2666
inode_set_ctime include/linux/fs.h:1773 [inline]
v9fs_stat2inode_dotl+0x4f6/0xad0 fs/9p/vfs_inode_dotl.c:656
v9fs_qid_iget_dotl fs/9p/vfs_inode_dotl.c:128 [inline]
v9fs_inode_from_fid_dotl+0x206/0x2b0 fs/9p/vfs_inode_dotl.c:154
v9fs_get_new_inode_from_fid fs/9p/v9fs.h:251 [inline]
v9fs_mount+0x6cb/0xa10 fs/9p/vfs_super.c:142
legacy_get_tree+0xfa/0x1a0 fs/fs_context.c:666
vfs_get_tree+0x8f/0x2b0 fs/super.c:1802
do_new_mount+0x24a/0xa40 fs/namespace.c:3856
do_mount fs/namespace.c:4193 [inline]
__do_sys_mount fs/namespace.c:4404 [inline]
__se_sys_mount+0x317/0x410 fs/namespace.c:4381
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f90546eea09
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 1f 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f9054699218 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f90547706e8 RCX: 00007f90546eea09
RDX: 0000200000000b80 RSI: 0000200000000040 RDI: 0000000000000000
RBP: 00007f90547706e0 R08: 0000200000000580 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f905473ca1c
R13: 0000200000000580 R14: 0000200000000040 R15: 00007f905473c04d
</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@...glegroups.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
Powered by blists - more mailing lists