syzbot


INFO: task hung in hfsplus_find_init

Status: upstream: reported C repro on 2025/12/15 15:07
Reported-by: syzbot+a540fd9be077e4464554@syzkaller.appspotmail.com
First crash: 5d06h, last: 1d06h
Bug presence (1)
Date Name Commit Repro Result
2025/12/17 upstream (ToT) ea1013c15392 C Failed due to an error; will retry later
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in hfsplus_find_init origin:upstream 1 C 12 1d21h 18d 0/3 upstream: reported C repro on 2025/12/01 22:56
upstream INFO: task hung in hfsplus_find_init hfs 1 C error done 1 731d 825d 25/29 fixed on 2024/01/31 13:17
upstream INFO: task hung in hfsplus_find_init (3) hfs 1 C error 20 2d11h 141d 0/29 upstream: reported C repro on 2025/08/01 17:38
upstream INFO: task hung in hfsplus_find_init (2) hfs 1 1 450d 450d 0/29 auto-obsoleted due to no activity on 2024/12/25 06:58

Sample crash report:
INFO: task kworker/u4:1:12 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:1    state:D
 stack:23384 pid:12    ppid:2      flags:0x00004000
Workqueue: writeback wb_workfn
 (flush-7:0)
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5380 [inline]
 __schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
 schedule+0xbd/0x170 kernel/sched/core.c:6773
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6832
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x6b7/0xcc0 kernel/locking/mutex.c:747
 hfsplus_find_init+0x154/0x1d0 fs/hfsplus/bfind.c:28
 hfsplus_cat_write_inode+0x1e7/0x7b0 fs/hfsplus/inode.c:593
 write_inode fs/fs-writeback.c:1483 [inline]
 __writeback_single_inode+0x705/0xee0 fs/fs-writeback.c:1700
 writeback_sb_inodes+0x77c/0xef0 fs/fs-writeback.c:1926
 __writeback_inodes_wb+0x111/0x240 fs/fs-writeback.c:1997
 wb_writeback+0x464/0xba0 fs/fs-writeback.c:2107
 wb_check_background_flush fs/fs-writeback.c:2177 [inline]
 wb_do_writeback fs/fs-writeback.c:2265 [inline]
 wb_workfn+0xb32/0xe20 fs/fs-writeback.c:2292
 process_one_work kernel/workqueue.c:2634 [inline]
 process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
 worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>

Showing all locks held in the system:
4 locks held by kworker/u4:1/12:
 #0: ffff888019e6a938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #0: ffff888019e6a938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #1: ffffc90000117d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
 #1: ffffc90000117d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
 #2: ffff88802f88e0e0 (&type->s_umount_key#45){++++}-{3:3}, at: super_trylock_shared+0x20/0xf0 fs/super.c:607
 #3: ffff88807a5440b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x154/0x1d0 fs/hfsplus/bfind.c:28
1 lock held by khungtaskd/29:
 #0: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}
, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
5 locks held by kworker/u4:10/2970:
2 locks held by getty/5526:
 #0: 
ffff88814ca220a0
 (
&tty->ldisc_sem
){++++}-{0:0}
, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: 
ffffc900015a72f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x425/0x1380 drivers/tty/n_tty.c:2217
6 locks held by syz-executor261/5759:

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

NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x39b/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xf41/0xf80 kernel/hung_task.c:379
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5759 Comm: syz-executor261 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:io_serial_in+0x77/0xb0 drivers/tty/serial/8250/8250_port.c:417
Code: e8 8e fb e8 fc 44 89 f9 d3 e3 49 83 c6 40 4c 89 f0 48 c1 e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 5f 69 40 fd 41 03 1e 89 da ec <0f> b6 c0 5b 41 5c 41 5e 41 5f c3 44 89 f9 80 e1 07 38 c1 7c aa 4c
RSP: 0018:ffffc900044e6bb8 EFLAGS: 00000006
RAX: 1ffffffff2e38805 RBX: 00000000000003f9 RCX: 0000000000000000
RDX: 00000000000003f9 RSI: 0000000000000000 RDI: 0000000000000020
RBP: ffffc900044e6db0 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff5200089cd58 R12: dffffc0000000000
R13: 0000000000000000 R14: ffffffff971c4240 R15: 0000000000000000
FS:  000055558e1a0380(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056529c325af0 CR3: 0000000077b52000 CR4: 00000000003506e0
Call Trace:
 <TASK>
 serial_port_in include/linux/serial_core.h:673 [inline]
 serial8250_console_write+0x24b/0x17a0 drivers/tty/serial/8250/8250_port.c:3438
 console_emit_next_record kernel/printk/printk.c:2944 [inline]
 console_flush_all+0x6cd/0xd00 kernel/printk/printk.c:3000
 console_unlock+0xae/0x340 kernel/printk/printk.c:3069
 vprintk_emit+0x477/0x600 kernel/printk/printk.c:2341
 _printk+0xd0/0x110 kernel/printk/printk.c:2366
 hfsplus_bnode_read_u16 fs/hfsplus/bnode.c:60 [inline]
 hfsplus_bnode_dump+0x321/0x440 fs/hfsplus/bnode.c:362
 hfsplus_brec_remove+0x47a/0x550 fs/hfsplus/brec.c:229
 __hfsplus_delete_attr+0x1d5/0x360 fs/hfsplus/attributes.c:299
 hfsplus_delete_attr+0x232/0x2d0 fs/hfsplus/attributes.c:345
 __hfsplus_setxattr+0x48a/0x1f00 fs/hfsplus/xattr.c:346
 hfsplus_setxattr+0x11e/0x170 fs/hfsplus/xattr.c:438
 hfsplus_trusted_setxattr+0x40/0x50 fs/hfsplus/xattr_trusted.c:30
 __vfs_setxattr+0x431/0x470 fs/xattr.c:201
 __vfs_setxattr_noperm+0x12d/0x5e0 fs/xattr.c:235
 vfs_setxattr+0x16c/0x2f0 fs/xattr.c:322
 do_setxattr fs/xattr.c:630 [inline]
 path_setxattr+0x362/0x550 fs/xattr.c:659
 __do_sys_lsetxattr fs/xattr.c:684 [inline]
 __se_sys_lsetxattr fs/xattr.c:680 [inline]
 __x64_sys_lsetxattr+0xb8/0xd0 fs/xattr.c:680
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa225872e99
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff3b3cced8 EFLAGS: 00000246 ORIG_RAX: 00000000000000bd
RAX: ffffffffffffffda RBX: 00002000000001c0 RCX: 00007fa225872e99
RDX: 00002000000001c0 RSI: 0000200000000180 RDI: 00002000000001c0
RBP: 0000200000000180 R08: 0000000000000000 R09: 000055558e1a14c0
R10: 0000000000000361 R11: 0000000000000246 R12: 0031656c69662f2e
R13: 0072657070752e79 R14: 431bde82d7b634db R15: 00007fa2258bc03b
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.767 msecs

Crashes (13):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/18 05:18 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
2025/12/18 00:19 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
2025/12/17 18:58 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
2025/12/17 14:25 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
2025/12/17 09:46 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
2025/12/17 00:00 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
2025/12/16 18:27 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
2025/12/16 13:55 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
2025/12/16 09:37 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
2025/12/16 04:46 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
2025/12/15 20:03 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
2025/12/19 14:38 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
2025/12/15 15:06 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan INFO: task hung in hfsplus_find_init
* Struck through repros no longer work on HEAD.