syzbot


possible deadlock in hfs_find_init

Status: upstream: reported C repro on 2025/06/17 20:55
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+949537796ff26787d134@syzkaller.appspotmail.com
First crash: 310d, last: 10h01m
Fix bisection: failed (error log, bisect log)
  
Bug presence (1)
Date Name Commit Repro Result
2025/12/04 upstream (ToT) 2aa680df6806 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-5.15 possible deadlock in hfs_find_init origin:upstream 4 C error 239 4d06h 1128d 0/3 upstream: reported C repro on 2023/03/22 23:14
linux-4.14 possible deadlock in hfs_find_init hfs 4 C 1 1150d 1183d 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 1145d 1210d 0/1 upstream: reported C repro on 2022/12/30 06:08
upstream possible deadlock in hfs_find_init (2) hfs 4 C error 7645 20m 1214d 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 409 5d14h 1130d 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 1932d 2923d 20/29 fixed on 2021/11/10 00:50

Sample crash report:
syz.0.17[5918]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
loop0: detected capacity change from 0 to 64
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.17/5918 is trying to acquire lock:
ffff88807b4900b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfs_find_init+0x17e/0x1f0 fs/hfs/bfind.c:-1

but task is already holding lock:
ffff88807b4900b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfs_find_init+0x17e/0x1f0 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/5918:
 #0: ffff88802e232418 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:412
 #1: ffff88802cf402b8 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline]
 #1: ffff88802cf402b8 (&sb->s_type->i_mutex_key#20){+.+.}-{3:3}, at: do_truncate+0x19c/0x240 fs/open.c:64
 #2: ffff88802cf400f8 (&HFS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfs_extend_file+0xff/0x1380 fs/hfs/extent.c:397
 #3: ffff88807b4900b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfs_find_init+0x17e/0x1f0 fs/hfs/bfind.c:-1
 #4: ffff888024bf80f8 (&HFS_I(tree->inode)->extents_lock){+.+.}-{3:3}, at: hfs_extend_file+0xff/0x1380 fs/hfs/extent.c:397

stack backtrace:
CPU: 0 PID: 5918 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
 check_deadlock kernel/locking/lockdep.c:3062 [inline]
 validate_chain kernel/locking/lockdep.c:3856 [inline]
 __lock_acquire+0x5dbc/0x7d40 kernel/locking/lockdep.c:5137
 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x136/0xcc0 kernel/locking/mutex.c:747
 hfs_find_init+0x17e/0x1f0 fs/hfs/bfind.c:-1
 hfs_ext_read_extent fs/hfs/extent.c:200 [inline]
 hfs_extend_file+0x361/0x1380 fs/hfs/extent.c:401
 hfs_bmap_reserve+0x107/0x430 fs/hfs/btree.c:269
 __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+0x3a0/0x1380 fs/hfs/extent.c:401
 hfs_get_block+0x413/0xc50 fs/hfs/extent.c:353
 __block_write_begin_int+0x57f/0x1af0 fs/buffer.c:2124
 __block_write_begin fs/buffer.c:2173 [inline]
 block_write_begin+0x9a/0x1e0 fs/buffer.c:2234
 cont_write_begin+0x5ee/0x810 fs/buffer.c:2591
 hfs_write_begin+0x8b/0xd0 fs/hfs/inode.c:58
 cont_expand_zero fs/buffer.c:2518 [inline]
 cont_write_begin+0x2b1/0x810 fs/buffer.c:2581
 hfs_write_begin+0x8b/0xd0 fs/hfs/inode.c:58
 hfs_file_truncate+0x1c4/0xa10 fs/hfs/extent.c:494
 hfs_inode_setattr+0x4af/0x6e0 fs/hfs/inode.c:659
 notify_change+0xb0d/0xe10 fs/attr.c:499
 do_truncate+0x1b0/0x240 fs/open.c:66
 vfs_truncate+0x266/0x300 fs/open.c:112
 do_sys_truncate+0xf6/0x1c0 fs/open.c:135
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f4f8eb9c819
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:00007fff817e50d8 EFLAGS: 00000246 ORIG_RAX: 000000000000004c
RAX: ffffffffffffffda RBX: 00007f4f8ee15fa0 RCX: 00007f4f8eb9c819
RDX: 0000000000000000 RSI: 0000000002fffffd RDI: 0000200000000940
RBP: 00007f4f8ec32c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f4f8ee15fac R14: 00007f4f8ee15fa0 R15: 00007f4f8ee15fa0
 </TASK>

Crashes (86):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/20 13:41 linux-6.6.y 9760bf04666d 303e2802 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/12/04 03:42 linux-6.6.y 4791134e4aeb d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/04/23 16:40 linux-6.6.y 9760bf04666d 4c3406dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/04/21 19:41 linux-6.6.y 9760bf04666d 0b6ab7ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/04/21 07:14 linux-6.6.y 9760bf04666d 3f2e655b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/04/20 12:26 linux-6.6.y 9760bf04666d 303e2802 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/04/16 18:41 linux-6.6.y 8cee53b8eaeb 4743f87d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/04/15 03:09 linux-6.6.y 8cee53b8eaeb e2e976a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/04/14 21:31 linux-6.6.y 8cee53b8eaeb 362d1323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/03/10 07:09 linux-6.6.y 4fc00fe35d46 6972f302 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/03/08 04:25 linux-6.6.y 4fc00fe35d46 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/02/23 10:47 linux-6.6.y 7a137e9bfa0e 6beca497 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/02/16 14:54 linux-6.6.y ae462074fde3 5d52cba5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/02/12 16:46 linux-6.6.y 1b4ef5214f17 504cb1bf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/02/10 23:46 linux-6.6.y c56aaf1a85ae 441e25b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/02/10 11:42 linux-6.6.y c56aaf1a85ae 91d776d3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/02/07 18:22 linux-6.6.y c56aaf1a85ae 4c131dc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/02/07 18:20 linux-6.6.y c56aaf1a85ae 4c131dc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/02/06 17:45 linux-6.6.y c56aaf1a85ae 97745f52 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/02/06 12:20 linux-6.6.y 2cf6f68313dc 97745f52 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/02/03 22:01 linux-6.6.y 2cf6f68313dc 42b01fab .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/01/26 12:51 linux-6.6.y cbb31f77b879 a4c52dd6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/01/24 01:44 linux-6.6.y cbb31f77b879 4f25b9b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/01/05 04:46 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/01/02 22:45 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/01/02 01:19 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2026/01/01 23:57 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/12/27 08:07 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/12/15 09:02 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/12/11 16:52 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/12/04 03:02 linux-6.6.y 4791134e4aeb d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/11/23 17:09 linux-6.6.y 0a805b6ea8cd 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/11/23 17:04 linux-6.6.y 0a805b6ea8cd 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/11/23 16:57 linux-6.6.y 0a805b6ea8cd 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/11/23 16:54 linux-6.6.y 0a805b6ea8cd 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/11/23 16:46 linux-6.6.y 0a805b6ea8cd 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/11/22 14:17 linux-6.6.y 0a805b6ea8cd 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/10/13 18:21 linux-6.6.y 655054d2c3c1 b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/10/09 09:17 linux-6.6.y e617101e5626 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/10/08 00:31 linux-6.6.y e617101e5626 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/09/19 13:20 linux-6.6.y 60a9e718726f 67c37560 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/09/19 13:20 linux-6.6.y 60a9e718726f 67c37560 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/09/19 13:20 linux-6.6.y 60a9e718726f 67c37560 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/09/17 11:27 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/09/17 10:37 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/09/16 17:07 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/08/16 10:49 linux-6.6.y bb9c90ab9c5a 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/06/27 23:01 linux-6.6.y 3f5b4c104b7d fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
2025/06/17 20:54 linux-6.6.y c2603c511feb e77fae15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in hfs_find_init
* Struck through repros no longer work on HEAD.