[v5.15] INFO: task hung in hfsplus_find_init

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cc5ec8769306 Linux 5.15.196
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14e7d8c2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=8c954c4ddd1a7be135e8
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c71c660545b2/disk-cc5ec876.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4f011826cca6/vmlinux-cc5ec876.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8ccd1a2c3f8c/bzImage-cc5ec876.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8c954c...@syzkaller.appspotmail.com

INFO: task kworker/u4:13:4413 blocked for more than 149 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:13 state:D stack:21512 pid: 4413 ppid: 2 flags:0x00004000
Workqueue: writeback wb_workfn (flush-7:2)
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6537
__mutex_lock_common+0xc71/0x2390 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28
hfsplus_cat_write_inode+0x1e3/0x820 fs/hfsplus/inode.c:588
write_inode fs/fs-writeback.c:1505 [inline]
__writeback_single_inode+0x6c3/0xda0 fs/fs-writeback.c:1715
writeback_sb_inodes+0x9fe/0x1610 fs/fs-writeback.c:1940
__writeback_inodes_wb+0x12a/0x3f0 fs/fs-writeback.c:2011
wb_writeback+0x455/0xb90 fs/fs-writeback.c:2116
wb_check_background_flush fs/fs-writeback.c:2182 [inline]
wb_do_writeback fs/fs-writeback.c:2270 [inline]
wb_workfn+0xb47/0xe60 fs/fs-writeback.c:2298
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c760 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
3 locks held by kworker/u4:2/145:
2 locks held by kworker/u4:4/1238:
#0: ffff888016879138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc900051d7d00 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
2 locks held by getty/3951:
#0: ffff88802c4aa098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900025ce2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
3 locks held by kworker/0:12/4379:
#0: ffff888016870938 ((wq_completion)events){+.+.}-{0:0}
, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1:
ffffc900045ffd00 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8c1211e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#2: ffffffff8c1211e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x6b0 kernel/rcu/tree_exp.h:845
2 locks held by kworker/0:18/4387:
#0:
ffff888016872138
((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc900049afd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
4 locks held by kworker/u4:13/4413:
#0: ffff888018dc0938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90004ba7d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2:
ffff888021f7a0e0 (&type->s_umount_key#64){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
#3: ffff8880540480b0 (&tree->tree_lock){+.+.}-{3:3}
, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28
3 locks held by syz.2.18/4451:
4 locks held by kworker/u4:14/4547:
#0: ffff8880169cd938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90003ab7d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8d22cd10 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x132/0xb80 net/core/net_namespace.c:589
#3: ffffffff8d238988 (rtnl_mutex){+.+.}-{3:3}, at: fib6_rules_net_exit+0xe/0x50 net/ipv6/fib6_rules.c:506
3 locks held by kworker/1:18/4685:
#0: ffff888016870938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90003b57d00 (fqdir_free_work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8c1210f0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0xa1/0x4b0 kernel/rcu/tree.c:4043
3 locks held by kworker/u4:16/5175:
1 lock held by syz-executor/5202:
#0: ffffffff8c1211e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#0: ffffffff8c1211e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x347/0x6b0 kernel/rcu/tree_exp.h:845
2 locks held by syz-executor/5617:
#0: ffff888020179118 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xf9/0x7d0 block/bdev.c:915
#1: ffff888020555468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xaa/0xb90 drivers/block/loop.c:1366
2 locks held by syz-executor/5725:
#0: ffff888020189d18 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xf9/0x7d0 block/bdev.c:915
#1: ffff888020584468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xaa/0xb90 drivers/block/loop.c:1366
1 lock held by syz-executor/6289:
#0: ffffffff8d238988 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d238988 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x7a5/0xe90 net/core/rtnetlink.c:5681

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 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
CPU: 1 PID: 1238 Comm: kworker/u4:4 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Workqueue: bat_events batadv_nc_worker
RIP: 0010:bytes_is_nonzero mm/kasan/generic.c:85 [inline]
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:102 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:128 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:159 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:180 [inline]
RIP: 0010:kasan_check_range+0x77/0x290 mm/kasan/generic.c:189
Code: 0c 03 48 8d 5c 37 ff 48 c1 eb 03 4e 8d 14 3b 4d 89 d6 4d 29 ce 49 83 fe 10 7f 26 4d 85 f6 0f 84 39 01 00 00 48 f7 d3 4c 01 db <41> 80 39 00 0f 85 c1 01 00 00 49 ff c1 48 ff c3 75 ee e9 1c 01 00
RSP: 0018:ffffc900051d7800 EFLAGS: 00000086
RAX: 0000000000000001 RBX: ffffffffffffffff RCX: ffffffff815c0836
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8ffbe1b0
RBP: ffffc900051d7a70 R08: dffffc0000000000 R09: fffffbfff1ff7c36
R10: fffffbfff1ff7c37 R11: 1ffffffff1ff7c36 R12: ffff8880220be450
R13: ffff8880220be404 R14: 0000000000000001 R15: dffffc0000000001
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055a8b8c0f950 CR3: 0000000029fae000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
instrument_atomic_read include/linux/instrumented.h:71 [inline]
test_bit include/asm-generic/bitops/instrumented-non-atomic.h:134 [inline]
hlock_class kernel/locking/lockdep.c:197 [inline]
check_wait_context kernel/locking/lockdep.c:4711 [inline]
__lock_acquire+0x916/0x7c60 kernel/locking/lockdep.c:4962
lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:313
rcu_read_lock include/linux/rcupdate.h:740 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:412 [inline]
batadv_nc_worker+0xc9/0x5c0 net/batman-adv/network-coding.c:723
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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 syzk...@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 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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: cc5ec8769306 Linux 5.15.196
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=1196a192580000

kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=8c954c4ddd1a7be135e8
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141242b4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=160d6512580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c71c660545b2/disk-cc5ec876.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4f011826cca6/vmlinux-cc5ec876.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8ccd1a2c3f8c/bzImage-cc5ec876.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/7c0f4c7e4b42/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8c954c...@syzkaller.appspotmail.com

INFO: task kworker/u4:1:144 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:22824 pid: 144 ppid: 2 flags:0x00004000
Workqueue: writeback wb_workfn
(flush-7:0)

4 locks held by kworker/u4:0/9:
#0: ffff8880193f8938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90000ce7d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}

, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2:

ffff888078abc0e0
(
&type->s_umount_key
#54

){.+.+}-{3:3}
, at: trylock_super+0x1c/0xf0 fs/super.c:418
#3:

ffff888078e0c0b0
(
&tree->tree_lock

){+.+.}-{3:3}
, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28

1 lock held by khungtaskd/27:
#0:
ffffffff8c11c760 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30

4 locks held by kworker/u4:1/144:
#0: ffff8880193f8938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc900011ffd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff8880745360e0 (&type->s_umount_key#54){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
#3: ffff88807db960b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28
4 locks held by kworker/u4:2/154:
#0: ffff8880193f8938
(
(wq_completion)writeback

){+.+.}-{0:0}
, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1:

ffffc90001b17d00
(
(work_completion)(&(&wb->dwork)->work)

){+.+.}-{0:0}
, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2:

ffff88805af3c0e0
(
&type->s_umount_key
#54){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
#3: ffff88805af380b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28
4 locks held by kworker/u4:3/410:
#0: ffff8880193f8938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90002affd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff88805962a0e0 (&type->s_umount_key#54){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
#3: ffff88805814a0b0 (&tree->tree_lock){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28
1 lock held by udevd/3561:
#0: ffff88801fdded18 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x157/0xa60 block/bdev.c:820
2 locks held by getty/3945:
#0:
ffff88802bade098
(
&tty->ldisc_sem

){++++}-{0:0}
, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1:

ffffc90002cf62e8
(
&ldata->atomic_read_lock

){+.+.}-{3:3}
, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158

4 locks held by kworker/u4:5/4340:
#0:
ffff8880193f8938
(
(wq_completion)writeback

){+.+.}-{0:0}
, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1:

ffffc90002fefd00
(
(work_completion)(&(&wb->dwork)->work)

){+.+.}-{0:0}
, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2:

ffff888024ad00e0
(
&type->s_umount_key
#54

){.+.+}-{3:3}
, at: trylock_super+0x1c/0xf0 fs/super.c:418
#3:

---
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.