syzbot


INFO: task hung in ext4_stop_mmpd (3)

Status: upstream: reported C repro on 2025/03/03 17:11
Reported-by: syzbot+13b8de76bda8c4760b9a@syzkaller.appspotmail.com
First crash: 9d21h, last: 8d06h
Bug presence (1)
Date Name Commit Repro Result
2025/03/04 upstream (ToT) 99fa936e8e4f C Failed due to an error; will retry later
Similar bugs (6)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in ext4_stop_mmpd ext4 C done done 483 173d 246d 28/28 fixed on 2024/10/28 16:40
linux-5.15 INFO: task hung in ext4_stop_mmpd 4 658d 695d 0/3 auto-obsoleted due to no activity on 2023/09/02 02:03
linux-5.15 INFO: task hung in ext4_stop_mmpd (2) 39 121d 252d 0/3 auto-obsoleted due to no activity on 2025/01/21 06:29
linux-6.1 INFO: task hung in ext4_stop_mmpd 146 147d 251d 0/3 auto-obsoleted due to no activity on 2024/12/25 21:49
upstream INFO: task can't die in ext4_stop_mmpd ext4 C inconclusive error 22 863d 1238d 0/28 auto-obsoleted due to no activity on 2023/04/21 15:51
upstream INFO: task can't die in p9_fd_close C done 58 1053d 1660d 0/28 closed as dup on 2022/08/26 12:44

Sample crash report:
INFO: task syz-executor917:4183 blocked for more than 143 seconds.
      Not tainted 5.15.178-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor917 state:D stack:25520 pid: 4183 ppid:  4179 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5027 [inline]
 __schedule+0x12c4/0x45b0 kernel/sched/core.c:6373
 schedule+0x11b/0x1f0 kernel/sched/core.c:6456
 schedule_timeout+0xac/0x300 kernel/time/timer.c:1890
 do_wait_for_common+0x2d9/0x480 kernel/sched/completion.c:85
 __wait_for_common kernel/sched/completion.c:106 [inline]
 wait_for_common kernel/sched/completion.c:117 [inline]
 wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
 kthread_stop+0x178/0x580 kernel/kthread.c:666
 ext4_stop_mmpd+0x43/0xb0 fs/ext4/mmp.c:263
 ext4_fill_super+0x6d67/0xa110 fs/ext4/super.c:5089
 mount_bdev+0x2c9/0x3f0 fs/super.c:1400
 legacy_get_tree+0xeb/0x180 fs/fs_context.c:611
 vfs_get_tree+0x88/0x270 fs/super.c:1530
 do_new_mount+0x2ba/0xb40 fs/namespace.c:3012
 do_mount fs/namespace.c:3355 [inline]
 __do_sys_mount fs/namespace.c:3563 [inline]
 __se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3540
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f060b6950fa
RSP: 002b:00007ffc024b3a78 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffc024b3a90 RCX: 00007f060b6950fa
RDX: 0000400000000040 RSI: 0000400000000000 RDI: 00007ffc024b3a90
RBP: 0000400000000040 R08: 00007ffc024b3ad0 R09: 00007ffc024b3ad0
R10: 0000000003010008 R11: 0000000000000202 R12: 0000400000000000
R13: 00007ffc024b3ad0 R14: 0000000000000003 R15: 0000000003010008
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8cb1fce0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3926:
 #0: ffff88802cf4d098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc900025c62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
1 lock held by syz-executor917/4183:
 #0: ffff88807a8760e0 (&type->s_umount_key#28/1){+.+.}-{3:3}, at: alloc_super+0x210/0x940 fs/super.c:229

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.178-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
 watchdog+0xe72/0xeb0 kernel/hung_task.c:295
 kthread+0x3f6/0x4f0 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt drivers/acpi/processor_idle.c:108 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:562

Crashes (11):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/05 08:15 linux-5.15.y c16c81c81336 c3901742 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in ext4_stop_mmpd
2025/03/05 04:35 linux-5.15.y c16c81c81336 c3901742 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in ext4_stop_mmpd
2025/03/05 00:43 linux-5.15.y c16c81c81336 c3901742 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in ext4_stop_mmpd
2025/03/04 20:06 linux-5.15.y c16c81c81336 c3901742 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in ext4_stop_mmpd
2025/03/04 14:23 linux-5.15.y c16c81c81336 c3901742 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in ext4_stop_mmpd
2025/03/04 10:46 linux-5.15.y c16c81c81336 c3901742 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in ext4_stop_mmpd
2025/03/04 07:14 linux-5.15.y c16c81c81336 c3901742 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in ext4_stop_mmpd
2025/03/04 03:48 linux-5.15.y c16c81c81336 c3901742 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in ext4_stop_mmpd
2025/03/04 00:16 linux-5.15.y c16c81c81336 c3901742 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in ext4_stop_mmpd
2025/03/03 20:45 linux-5.15.y c16c81c81336 c3901742 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan INFO: task hung in ext4_stop_mmpd
2025/03/03 17:10 linux-5.15.y c16c81c81336 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in ext4_stop_mmpd
* Struck through repros no longer work on HEAD.