syzbot


INFO: task hung in lmLogClose

Status: upstream: reported C repro on 2024/04/05 11:21
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+f6eb2331cbd10f200097@syzkaller.appspotmail.com
First crash: 298d, last: 4d17h
Bug presence (1)
Date Name Commit Repro Result
2025/01/19 upstream (ToT) fda5e3f28400 C [report] INFO: task hung in lmLogClose
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in lmLogClose jfs 1 652d 652d 0/28 auto-obsoleted due to no activity on 2023/07/16 16:14
upstream INFO: task hung in lmLogClose (3) jfs C error 287 4d10h 315d 0/28 upstream: reported C repro on 2024/03/19 10:13
linux-6.1 INFO: task hung in lmLogClose origin:upstream C 21 3d18h 261d 0/3 upstream: reported C repro on 2024/05/12 07:21
upstream INFO: task hung in lmLogClose (2) jfs C inconclusive done 5 384d 476d 25/28 fixed on 2024/02/24 00:02

Sample crash report:
INFO: task syz-executor399:4183 blocked for more than 143 seconds.
      Not tainted 5.15.176-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor399 state:D stack:26176 pid: 4183 ppid:  4179 flags:0x00004002
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_preempt_disabled+0xf/0x20 kernel/sched/core.c:6515
 __mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452
 jfs_umount+0x298/0x370 fs/jfs/jfs_umount.c:116
 jfs_put_super+0x86/0x180 fs/jfs/super.c:194
 generic_shutdown_super+0x130/0x310 fs/super.c:475
 kill_block_super+0x7a/0xe0 fs/super.c:1427
 deactivate_locked_super+0xa0/0x110 fs/super.c:335
 cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
 task_work_run+0x129/0x1a0 kernel/task_work.c:188
 tracehook_notify_resume include/linux/tracehook.h:189 [inline]
 exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:181
 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214
 __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
 syscall_exit_to_user_mode+0x5d/0x240 kernel/entry/common.c:307
 do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fcb524b35f7
RSP: 002b:00007ffff6589228 EFLAGS: 00000206 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fcb524b35f7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffff65892e0
RBP: 00007ffff65892e0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000206 R12: 00007ffff658a350
R13: 000055558115f6c0 R14: 431bde82d7b634db R15: 00007ffff658a370
 </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: ffff88802c32b098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc90002cd62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
1 lock held by syz-executor399/4180:
 #0: ffff88807db400e0 (&type->s_umount_key#43){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
2 locks held by syz-executor399/4181:
 #0: ffff88807dc800e0 (&type->s_umount_key#43){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
 #1: ffffffff8cecbae8 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452
2 locks held by syz-executor399/4182:
 #0: ffff88802c3380e0 (&type->s_umount_key#43){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
 #1: ffffffff8cecbae8 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452
2 locks held by syz-executor399/4183:
 #0: ffff8880781360e0 (&type->s_umount_key#43){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
 #1: ffffffff8cecbae8 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452
2 locks held by syz-executor399/4184:
 #0: ffff88807e5320e0 (&type->s_umount_key#43){+.+.}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
 #1: ffffffff8cecbae8 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xae/0x530 fs/jfs/jfs_logmgr.c:1452

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.176-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
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 (12):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/01/19 10:35 linux-5.15.y 4735586da88e f2cb035c .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan INFO: task hung in lmLogClose
2025/01/24 04:48 linux-5.15.y 003148680b79 521b0ce3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 INFO: task hung in lmLogClose
2025/01/21 17:59 linux-5.15.y 4735586da88e da72ac06 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in lmLogClose
2024/10/27 15:20 linux-5.15.y 74cdd62cb470 65e8686b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in lmLogClose
2024/10/27 15:12 linux-5.15.y 74cdd62cb470 65e8686b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in lmLogClose
2024/10/27 15:12 linux-5.15.y 74cdd62cb470 65e8686b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in lmLogClose
2024/07/31 10:26 linux-5.15.y 7e89efd3ae1c 6fde257d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in lmLogClose
2024/05/30 02:32 linux-5.15.y c61bd26ae81a 34889ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in lmLogClose
2024/04/05 11:21 linux-5.15.y 9465fef4ae35 0ee3535e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in lmLogClose
2024/11/11 23:50 linux-5.15.y 3c17fc483905 0c4b1325 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in lmLogClose
2024/09/03 06:44 linux-5.15.y fa93fa65db6e 8045124c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in lmLogClose
2024/09/03 06:22 linux-5.15.y fa93fa65db6e 8045124c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in lmLogClose
* Struck through repros no longer work on HEAD.