syzbot


possible deadlock in hfs_find_init

Status: upstream: reported C repro on 2023/03/22 23:14
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+5ec6d29e9352c6f10dc7@syzkaller.appspotmail.com
First crash: 1119d, last: 13h13m
Fix bisection: failed (error log, bisect log)
  
Bug presence (1)
Date Name Commit Repro Result
2024/04/24 upstream (ToT) e88c4cfcb7b8 C [report] possible deadlock in hfs_find_init
Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 possible deadlock in hfs_find_init hfs 4 C 1 1142d 1174d 0/1 upstream: reported C repro on 2023/01/26 19:14
linux-4.19 possible deadlock in hfs_find_init hfs 4 C error 7 1136d 1202d 0/1 upstream: reported C repro on 2022/12/30 06:08
linux-6.6 possible deadlock in hfs_find_init origin:upstream 4 C error 78 12h41m 301d 0/2 upstream: reported C repro on 2025/06/17 20:55
upstream possible deadlock in hfs_find_init (2) hfs 4 C error 7533 1h57m 1205d 0/29 upstream: reported C repro on 2022/12/27 00:59
linux-6.1 possible deadlock in hfs_find_init origin:upstream 4 C 408 2d13h 1121d 0/3 upstream: reported C repro on 2023/03/20 17:38
upstream possible deadlock in hfs_find_init hfs 4 C done error 1 1924d 2914d 20/29 fixed on 2021/11/10 00:50
Last patch testing requests (10)
Created Duration User Patch Repo Result
2026/01/30 19:57 24m retest repro linux-5.15.y report log
2026/01/30 19:57 18m retest repro linux-5.15.y report log
2026/01/30 19:57 12m retest repro linux-5.15.y report log
2026/01/30 19:57 16m retest repro linux-5.15.y report log
2026/01/30 19:57 9m retest repro linux-5.15.y report log
2025/11/18 02:05 10m retest repro linux-5.15.y report log
2025/11/18 02:05 10m retest repro linux-5.15.y report log
2025/11/18 02:05 10m retest repro linux-5.15.y report log
2025/11/18 02:05 10m retest repro linux-5.15.y report log
2025/10/18 05:47 15m retest repro linux-5.15.y report log

Sample crash report:
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.17/4465 is trying to acquire lock:
ffff888079bfe0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfs_find_init+0x15b/0x1d0 fs/hfs/bfind.c:-1

but task is already holding lock:
ffff888079bfe0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfs_find_init+0x15b/0x1d0 fs/hfs/bfind.c:-1

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&tree->tree_lock/1);
  lock(&tree->tree_lock/1);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

5 locks held by syz.0.17/4465:
 #0: ffff88807655c460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:386
 #1: ffff88801b5b1628 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #1: ffff88801b5b1628 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: do_truncate+0x198/0x240 fs/open.c:63
 #2: ffff88801b5b1478 (&HFS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfs_extend_file+0xfb/0x13f0 fs/hfs/extent.c:397
 #3: ffff888079bfe0b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfs_find_init+0x15b/0x1d0 fs/hfs/bfind.c:-1
 #4: ffff88801b5b00f8 (&HFS_I(tree->inode)->extents_lock){+.+.}-{3:3}, at: hfs_extend_file+0xfb/0x13f0 fs/hfs/extent.c:397

stack backtrace:
CPU: 1 PID: 4465 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 __lock_acquire+0x1236/0x7d10 kernel/locking/lockdep.c:-1
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x1e3/0x2400 kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 hfs_find_init+0x15b/0x1d0 fs/hfs/bfind.c:-1
 hfs_ext_read_extent fs/hfs/extent.c:200 [inline]
 hfs_extend_file+0x35d/0x13f0 fs/hfs/extent.c:401
 hfs_bmap_reserve+0x103/0x420 fs/hfs/btree.c:231
 __hfs_ext_write_extent+0x1fa/0x470 fs/hfs/extent.c:121
 __hfs_ext_cache_extent+0x6b/0x9b0 fs/hfs/extent.c:174
 hfs_ext_read_extent fs/hfs/extent.c:202 [inline]
 hfs_extend_file+0x39c/0x13f0 fs/hfs/extent.c:401
 hfs_get_block+0x40f/0xc50 fs/hfs/extent.c:353
 __block_write_begin_int+0x565/0x15d0 fs/buffer.c:2012
 __block_write_begin fs/buffer.c:2062 [inline]
 block_write_begin fs/buffer.c:2122 [inline]
 cont_write_begin+0x598/0x7b0 fs/buffer.c:2471
 hfs_write_begin+0x92/0xe0 fs/hfs/inode.c:59
 cont_expand_zero fs/buffer.c:2398 [inline]
 cont_write_begin+0x263/0x7b0 fs/buffer.c:2461
 hfs_write_begin+0x92/0xe0 fs/hfs/inode.c:59
 hfs_file_truncate+0x1c2/0xa10 fs/hfs/extent.c:494
 hfs_inode_setattr+0x4ab/0x6f0 fs/hfs/inode.c:657
 notify_change+0xbcd/0xee0 fs/attr.c:505
 do_truncate+0x1ac/0x240 fs/open.c:65
 vfs_truncate+0x262/0x2f0 fs/open.c:111
 do_sys_truncate+0xf2/0x1c0 fs/open.c:134
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fd051f0f799
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffede059158 EFLAGS: 00000246 ORIG_RAX: 000000000000004c
RAX: ffffffffffffffda RBX: 00007fd052188fa0 RCX: 00007fd051f0f799
RDX: 0000000000000000 RSI: 0000000002fffffd RDI: 0000200000000940
RBP: 00007fd051fa5c99 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd052188fac R14: 00007fd052188fa0 R15: 00007fd052188fa0
 </TASK>

Crashes (238):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/03/25 17:29 linux-5.15.y 91d48252ad4b 8ee77f7d .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/14 23:13 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/09/15 06:08 linux-5.15.y 43bb85222e53 e2beed91 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/02/23 22:00 linux-5.15.y c16c81c81336 d34966d1 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2024/12/30 04:22 linux-5.15.y 91786f140358 d3ccff63 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2024/04/09 10:28 linux-5.15.y 9465fef4ae35 f3234354 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2023/07/23 02:21 linux-5.15.y d54cfc420586 27cbe77f .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2024/06/12 05:04 linux-5.15.y c61bd26ae81a 4d75f4f7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in hfs_find_init
2023/06/17 03:50 linux-5.15.y 471e639e59d1 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in hfs_find_init
2026/04/15 02:38 linux-5.15.y 91d48252ad4b e2e976a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/04/14 01:54 linux-5.15.y 91d48252ad4b 1a086e7c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/04/13 13:54 linux-5.15.y 91d48252ad4b 9530ccf9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/04/12 20:37 linux-5.15.y 91d48252ad4b 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/04/11 10:54 linux-5.15.y 91d48252ad4b 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/04/09 04:37 linux-5.15.y 91d48252ad4b 38c8e246 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/04/07 21:36 linux-5.15.y 91d48252ad4b 628666c6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/04/07 07:56 linux-5.15.y 91d48252ad4b 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/04/04 00:27 linux-5.15.y 91d48252ad4b 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/03/28 03:10 linux-5.15.y 91d48252ad4b 356bdfc9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/03/27 17:28 linux-5.15.y 91d48252ad4b 74a13a23 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/03/25 12:03 linux-5.15.y 91d48252ad4b 8ee77f7d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/03/23 16:16 linux-5.15.y 91d48252ad4b 4933dba2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/03/23 15:51 linux-5.15.y 91d48252ad4b 4933dba2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/03/20 03:40 linux-5.15.y 91d48252ad4b 2f245add .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/03/08 12:43 linux-5.15.y 91d48252ad4b 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/03/08 06:08 linux-5.15.y 91d48252ad4b 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/03/07 20:16 linux-5.15.y 91d48252ad4b 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/03/03 05:41 linux-5.15.y 3330a8d33e08 28b83e23 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/02/23 15:24 linux-5.15.y 3330a8d33e08 6beca497 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/02/15 06:26 linux-5.15.y e45d5d41c134 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/02/15 03:57 linux-5.15.y e45d5d41c134 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/02/07 15:38 linux-5.15.y 7b232985052f f20fc9f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/02/02 07:27 linux-5.15.y 9eec9a14ee10 6b8752f2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/01/16 15:24 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/01/13 15:55 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/01/09 03:52 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/01/03 07:04 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2026/01/02 02:29 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/31 17:06 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/31 15:51 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/28 18:30 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/27 07:03 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/26 21:30 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/25 12:02 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/24 08:30 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/22 03:53 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/21 23:02 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/20 09:27 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/19 15:39 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/16 21:26 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/12/05 19:00 linux-5.15.y cc5ec8769306 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/11/24 10:58 linux-5.15.y cc5ec8769306 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/11/03 11:20 linux-5.15.y cc5ec8769306 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/10/30 19:17 linux-5.15.y cc5ec8769306 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/10/27 05:57 linux-5.15.y ac56c046adf4 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in hfs_find_init
2025/08/17 10:45 linux-5.15.y c79648372d02 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in hfs_find_init
2023/03/22 23:13 linux-5.15.y 115472395b0a f94b4a29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in hfs_find_init
* Struck through repros no longer work on HEAD.