syzbot


possible deadlock in hfs_extend_file (3)

Status: upstream: reported C repro on 2024/04/18 14:41
Subsystems: hfs
[Documentation on labels]
Reported-by: syzbot+2a62f58f1a4951a549bb@syzkaller.appspotmail.com
First crash: 786d, last: 6h54m
Cause bisection: introduced by (bisect log) [merge commit]:
commit e8c3f6322cc853084a6d63244c15fb0251090327
Author: Arnd Bergmann <arnd@arndb.de>
Date: Thu Oct 11 13:21:40 2018 +0000

  Merge tag 'imx-defconfig-4.20' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into next/defconfig

Crash: lost connection to test machine (log)
Repro: C syz .config
  
✨ AI Jobs (4)
ID Workflow Result Correct Bug Created Started Finished Revision Error
351e65a9-c6a1-4933-9d55-ba6aeb5bf9ff assessment-security 💥 possible deadlock in hfs_extend_file (3) 2026/06/10 00:01 2026/06/10 00:01 2026/06/10 00:04 c36c07f6c1f2230a36374cbd22235f635e8f9284 failed to run ["make" "KERNELVERSION=syzkaller" "KERNELRELEASE=syzkaller" "LOCALVERSION=-syzkaller" "-j" "32" "ARCH=x86_64" "CC=ccache clang" "LD=ld.lld" "O=/app/workdir/cache/build/8eaa7e55ffdaf629e848aa4f7c928de19a59ab04" "-s" "bzImage" "compile_commands.json"]: exit status 2 Root cause: error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` error: aborting due to 2 previous errors * * Restart config... * * * Memory initialization * Initialize kernel stack variables at function entry 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE) 2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) > 3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) choice[1-3?]: 3 Poison kernel stack before returning from syscalls (KSTACK_ERASE) [N/y/?] (NEW) Error in reading or end of file. Enable heap memory zeroing on allocation by default (INIT_ON_ALLOC_DEFAULT_ON) [Y/n/?] y Enable heap memory zeroing on free by default (INIT_ON_FREE_DEFAULT_ON) [N/y/?] n Enable register zeroing on function exit (ZERO_CALL_USED_REGS) [N/y/?] n error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `core` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `core` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `compiler_builtins` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `compiler_builtins` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: aborting due to 2 previous errors make[3]: *** [/app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/rust/Makefile:527: rust/build_error.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[2]: *** [/app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/Makefile:1286: prepare] Error 2 make[1]: *** [/app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/Makefile:248: __sub-make] Error 2 make: *** [Makefile:248: __sub-make] Error 2
ceed0071-5cb0-406d-a7a0-1caf6d50dc3e assessment-security 💥 possible deadlock in hfs_extend_file (3) 2026/06/04 01:55 2026/06/04 01:55 2026/06/04 01:57 62fe15281f5011cd203d8845b8767b10e7443aa5 failed to run ["make" "KERNELVERSION=syzkaller" "KERNELRELEASE=syzkaller" "LOCALVERSION=-syzkaller" "-j" "32" "ARCH=x86_64" "CC=ccache clang" "LD=ld.lld" "O=/app/workdir/cache/build/8eaa7e55ffdaf629e848aa4f7c928de19a59ab04" "-s" "bzImage" "compile_commands.json"]: exit status 2 Root cause: error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` error: aborting due to 2 previous errors * * Restart config... * * * Memory initialization * Initialize kernel stack variables at function entry 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE) 2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) > 3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) choice[1-3?]: 3 Poison kernel stack before returning from syscalls (KSTACK_ERASE) [N/y/?] (NEW) Error in reading or end of file. Enable heap memory zeroing on allocation by default (INIT_ON_ALLOC_DEFAULT_ON) [Y/n/?] y Enable heap memory zeroing on free by default (INIT_ON_FREE_DEFAULT_ON) [N/y/?] n Enable register zeroing on function exit (ZERO_CALL_USED_REGS) [N/y/?] n error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `core` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `core` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `compiler_builtins` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `compiler_builtins` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: aborting due to 2 previous errors make[3]: *** [/app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/rust/Makefile:527: rust/build_error.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[2]: *** [/app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/Makefile:1286: prepare] Error 2 make[1]: *** [/app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/Makefile:248: __sub-make] Error 2 make: *** [Makefile:248: __sub-make] Error 2
57add41d-fe9d-4b02-8a49-0318fcd26cda assessment-security 💥 possible deadlock in hfs_extend_file (3) 2026/06/01 13:18 2026/06/01 13:18 2026/06/01 13:21 6b4a844333e83556da95d61d7f207e7ef5cd4bc6 failed to run ["make" "KERNELVERSION=syzkaller" "KERNELRELEASE=syzkaller" "LOCALVERSION=-syzkaller" "-j" "32" "ARCH=x86_64" "CC=ccache clang" "LD=ld.lld" "O=/app/workdir/cache/build/8eaa7e55ffdaf629e848aa4f7c928de19a59ab04" "-s" "bzImage" "compile_commands.json"]: exit status 2 Root cause: error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` error: aborting due to 2 previous errors * * Restart config... * * * Memory initialization * Initialize kernel stack variables at function entry 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE) 2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) > 3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) choice[1-3?]: 3 Poison kernel stack before returning from syscalls (KSTACK_ERASE) [N/y/?] (NEW) Error in reading or end of file. Enable heap memory zeroing on allocation by default (INIT_ON_ALLOC_DEFAULT_ON) [Y/n/?] y Enable heap memory zeroing on free by default (INIT_ON_FREE_DEFAULT_ON) [N/y/?] n Enable register zeroing on function exit (ZERO_CALL_USED_REGS) [N/y/?] n error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `core` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `core` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `compiler_builtins` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `compiler_builtins` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: aborting due to 2 previous errors make[3]: *** [/app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/rust/Makefile:527: rust/build_error.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[2]: *** [/app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/Makefile:1286: prepare] Error 2 make[1]: *** [/app/workdir/cache/src/517d7321164a402d7b933f33daa1cf0475aac159/Makefile:248: __sub-make] Error 2 make: *** [Makefile:248: __sub-make] Error 2
833efe6b-d5e6-4bc9-a58d-e84cdf9ec5f8 assessment-security 💥 possible deadlock in hfs_extend_file (3) 2026/05/15 22:32 2026/05/15 22:32 2026/05/15 22:34 efdaf0f9b8bfc56ea6d17bea15a64f4591cc712d failed to run ["make" "KERNELVERSION=syzkaller" "KERNELRELEASE=syzkaller" "LOCALVERSION=-syzkaller" "-j" "32" "ARCH=x86_64" "CC=ccache clang" "LD=ld.lld" "O=/app/workdir/cache/build/8eaa7e55ffdaf629e848aa4f7c928de19a59ab04" "-s" "bzImage" "compile_commands.json"]: exit status 2 Root cause: error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` error: aborting due to 2 previous errors * * Restart config... * * * Memory initialization * Initialize kernel stack variables at function entry 1. no automatic stack variable initialization (weakest) (INIT_STACK_NONE) 2. pattern-init everything (strongest) (INIT_STACK_ALL_PATTERN) > 3. zero-init everything (strongest and safest) (INIT_STACK_ALL_ZERO) choice[1-3?]: 3 Poison kernel stack before returning from syscalls (KSTACK_ERASE) [N/y/?] (NEW) Error in reading or end of file. Enable heap memory zeroing on allocation by default (INIT_ON_ALLOC_DEFAULT_ON) [Y/n/?] y Enable heap memory zeroing on free by default (INIT_ON_FREE_DEFAULT_ON) [N/y/?] n Enable register zeroing on function exit (ZERO_CALL_USED_REGS) [N/y/?] n error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/53ac2e7a9a1e64a74ef7dbfc938455cf249a2829/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `core` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `core` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: mixing `-Zsanitizer` will cause an ABI mismatch in crate `build_error` --> /app/workdir/cache/src/53ac2e7a9a1e64a74ef7dbfc938455cf249a2829/rust/build_error.rs:3:1 | 3 | //! Build-time error. | ^ | = help: the `-Zsanitizer` flag modifies the ABI so Rust crates compiled with different values of this flag cannot be used together safely = note: unset `-Zsanitizer` in this crate is incompatible with `-Zsanitizer=kernel-address` in dependency `compiler_builtins` = help: set `-Zsanitizer=kernel-address` in this crate or unset `-Zsanitizer` in `compiler_builtins` = help: if you are sure this will not cause problems, you may use `-Cunsafe-allow-abi-mismatch=sanitizer` to silence this error error: aborting due to 2 previous errors make[3]: *** [/app/workdir/cache/src/53ac2e7a9a1e64a74ef7dbfc938455cf249a2829/rust/Makefile:527: rust/build_error.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[2]: *** [/app/workdir/cache/src/53ac2e7a9a1e64a74ef7dbfc938455cf249a2829/Makefile:1286: prepare] Error 2 make[1]: *** [/app/workdir/cache/src/53ac2e7a9a1e64a74ef7dbfc938455cf249a2829/Makefile:248: __sub-make] Error 2 make: *** [Makefile:248: __sub-make] Error 2
Discussions (9)
Title Replies (including bot) Last reply
[syzbot] Monthly hfs report (Jun 2026) 0 (1) 2026/06/03 04:32
[syzbot] Monthly hfs report (May 2026) 0 (1) 2026/05/02 20:32
[syzbot] Monthly hfs report (Apr 2026) 0 (1) 2026/04/01 13:15
[syzbot] Monthly hfs report (Mar 2026) 0 (1) 2026/03/03 08:06
[syzbot] Monthly hfs report (Jan 2026) 0 (1) 2026/01/29 10:20
[syzbot] Monthly hfs report (Dec 2025) 0 (1) 2025/12/29 10:22
[syzbot] Monthly hfs report (Oct 2025) 0 (1) 2025/10/27 12:50
[syzbot] [hfs?] possible deadlock in hfs_extend_file (3) 0 (2) 2024/06/23 09:36
[PATCH fs/hfs] hfs: fix deadlock in hfs_extend_file() 1 (1) 2024/04/23 09:31
Similar bugs (9)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 possible deadlock in hfs_extend_file hfs 4 1 1260d 1260d 0/1 upstream: reported on 2022/12/27 15:22
linux-5.15 possible deadlock in hfs_extend_file (2) 4 1 960d 960d 0/3 auto-obsoleted due to no activity on 2024/01/31 18:25
linux-6.1 possible deadlock in hfs_extend_file 4 7 998d 1184d 0/3 auto-obsoleted due to no activity on 2023/12/24 21:20
upstream possible deadlock in hfs_extend_file hfs 4 46 1022d 1266d 0/29 auto-obsoleted due to no activity on 2023/11/06 09:48
linux-6.1 possible deadlock in hfs_extend_file (2) origin:upstream 4 C 231 18d 797d 0/3 upstream: reported C repro on 2024/04/04 03:11
linux-5.15 possible deadlock in hfs_extend_file (3) origin:upstream 4 C 212 18d 819d 0/3 upstream: reported C repro on 2024/03/13 05:11
linux-6.6 possible deadlock in hfs_extend_file origin:upstream missing-backport 4 C error 127 1d21h 357d 0/2 upstream: reported C repro on 2025/06/17 13:12
upstream possible deadlock in hfs_extend_file (2) hfs 4 C done done 4 890d 910d 0/29 auto-obsoleted due to no activity on 2024/04/11 05:11
linux-5.15 possible deadlock in hfs_extend_file 4 5 1086d 1149d 0/3 auto-obsoleted due to no activity on 2023/09/28 05:53
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/08/31 11:43 59m retest repro upstream report log

Sample crash report:
WARNING: The mand mount option has been deprecated and
         and is ignored by this kernel. Remove the mand
         option from the mount to silence this warning.
=======================================================
============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.17/5962 is trying to acquire lock:
ffff8880315e0128 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xda/0x14c0 fs/hfs/extent.c:397

but task is already holding lock:
ffff8880315e0868 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xda/0x14c0 fs/hfs/extent.c:397

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

       CPU0
       ----
  lock(&HFS_I(tree->inode)->extents_lock);
  lock(&HFS_I(tree->inode)->extents_lock);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

5 locks held by syz.0.17/5962:
 #0: ffff8880387b4480 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:508
 #1: ffff888030d20300 (&type->i_mutex_dir_key#8){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:980 [inline]
 #1: ffff888030d20300 (&type->i_mutex_dir_key#8){+.+.}-{4:4}, at: open_last_lookups fs/namei.c:3892 [inline]
 #1: ffff888030d20300 (&type->i_mutex_dir_key#8){+.+.}-{4:4}, at: path_openat+0x8e6/0x3840 fs/namei.c:4131
 #2: ffff88803866a0a0 (&tree->tree_lock){+.+.}-{4:4}, at: hfs_find_init+0x18e/0x2c0 fs/hfs/bfind.c:-1
 #3: ffff8880315e0868 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xda/0x14c0 fs/hfs/extent.c:397
 #4: ffff8880386680a0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfs_find_init+0x18e/0x2c0 fs/hfs/bfind.c:-1

stack backtrace:
CPU: 1 UID: 0 PID: 5962 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_deadlock_bug+0x28b/0x2a0 kernel/locking/lockdep.c:3041
 check_deadlock kernel/locking/lockdep.c:3093 [inline]
 validate_chain+0x1a3f/0x2140 kernel/locking/lockdep.c:3895
 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547
 hfs_extend_file+0xda/0x14c0 fs/hfs/extent.c:397
 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+0x31e/0x14c0 fs/hfs/extent.c:401
 hfs_bmap_reserve+0x107/0x430 fs/hfs/btree.c:269
 hfs_cat_create+0x1c5/0x730 fs/hfs/catalog.c:104
 hfs_create+0x66/0xe0 fs/hfs/dir.c:202
 lookup_open fs/namei.c:3796 [inline]
 open_last_lookups fs/namei.c:3895 [inline]
 path_openat+0x1500/0x3840 fs/namei.c:4131
 do_filp_open+0x1fa/0x410 fs/namei.c:4161
 do_sys_openat2+0x121/0x1c0 fs/open.c:1437
 do_sys_open fs/open.c:1452 [inline]
 __do_sys_open fs/open.c:1460 [inline]
 __se_sys_open fs/open.c:1456 [inline]
 __x64_sys_open+0x11e/0x150 fs/open.c:1456
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd0b1c0eec9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff6de76808 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007fd0b1e65fa0 RCX: 00007fd0b1c0eec9
RDX: 0000000000000000 RSI: 000000000014927e RDI: 0000200000000180
RBP: 00007fd0b1c91f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd0b1e65fa0 R14: 00007fd0b1e65fa0 R15: 0000000000000003
 </TASK>

Crashes (5754):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/10/10 14:43 upstream 5472d60c129f ff1712fe .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in hfs_extend_file
2024/06/23 09:36 upstream 563a50672d8a edc5149a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs possible deadlock in hfs_extend_file
2025/10/10 12:48 upstream 5472d60c129f ff1712fe .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root possible deadlock in hfs_extend_file
2024/12/13 13:29 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2e7aff49b5da 3547e30f .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-upstream-gce-arm64 possible deadlock in hfs_extend_file
2026/06/10 02:26 upstream 685441a6d3f1 34dab4be .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/09 23:41 upstream 2d3090a8aeb5 34dab4be .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/09 11:22 upstream 2d3090a8aeb5 c36c07f6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/09 03:53 upstream 4549871118cf 656e94c6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in hfs_extend_file
2026/06/08 14:47 upstream 4549871118cf 656e94c6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/08 10:32 upstream 4549871118cf cc095639 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/08 10:32 upstream 4549871118cf cc095639 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/07 20:56 upstream 33d8d8ec31b5 cc095639 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/07 07:14 upstream 979c294509f9 cc095639 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/06 04:01 upstream c10130c234c8 cc095639 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/05 11:56 upstream ddd664bbff63 197909be .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/03 23:48 upstream ba3e43a9e601 197909be .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/03 11:25 upstream ba3e43a9e601 234057e5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/03 02:41 upstream ba3e43a9e601 3c0d2131 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/02 11:06 upstream 6f3ed7fec72f 62fe1528 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/02 11:06 upstream 6f3ed7fec72f 62fe1528 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/02 09:21 upstream 6f3ed7fec72f 1095583b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfs_extend_file
2026/06/02 07:30 upstream 6f3ed7fec72f 1095583b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/01 21:22 upstream e43ffb69e043 1095583b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/01 08:55 upstream e43ffb69e043 8d8eeb3a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/06/01 03:18 upstream e43ffb69e043 6b4a8443 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/31 16:42 upstream 174914ea5513 6b4a8443 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfs_extend_file
2026/05/31 13:57 upstream 174914ea5513 6b4a8443 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/31 00:32 upstream 9d87d0fc8c8e 6b4a8443 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/30 11:04 upstream f5e5d3509bff 6b4a8443 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/29 21:50 upstream 9215e74f228f 6b4a8443 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/29 21:50 upstream 9215e74f228f 6b4a8443 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/29 00:17 upstream 8fde5d1d47f6 4624854e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/28 17:47 upstream eb3f4b7426cf 681715f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfs_extend_file
2026/05/28 11:06 upstream eb3f4b7426cf 9a5a7e5e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/28 06:54 upstream eb3f4b7426cf 4c36e7e5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfs_extend_file
2026/05/27 22:58 upstream eb3f4b7426cf 4c36e7e5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/26 22:48 upstream d60ec36cab33 2b01f00e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfs_extend_file
2026/05/26 21:18 upstream d60ec36cab33 2b01f00e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/26 20:16 upstream d60ec36cab33 a3e47276 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/26 08:37 upstream e8c2f9fdadee a3e47276 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/26 01:58 upstream e8c2f9fdadee c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/25 12:21 upstream e7ae89a0c97c c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2026/05/25 05:01 upstream 6a97c4d5262d c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfs_extend_file
2026/05/24 22:38 upstream 6a97c4d5262d c69befb3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfs_extend_file
2024/06/23 20:30 upstream 7c16f0a4ed1c edc5149a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in hfs_extend_file
2024/06/21 22:01 upstream 66cc544fd75c edc5149a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in hfs_extend_file
2024/04/14 14:39 upstream fe46a7dd189e c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in hfs_extend_file
2026/06/06 07:12 upstream 06121e12c27a cc095639 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfs_extend_file
2026/06/05 14:54 upstream ddd664bbff63 48b6c3fa .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfs_extend_file
2026/06/05 14:05 upstream ddd664bbff63 48b6c3fa .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfs_extend_file
2026/05/31 09:19 upstream 174914ea5513 6b4a8443 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfs_extend_file
2026/05/30 07:07 upstream 9215e74f228f 6b4a8443 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfs_extend_file
2026/05/28 02:45 upstream eb3f4b7426cf 4c36e7e5 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfs_extend_file
2024/06/04 08:08 upstream 2ab795141095 c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in hfs_extend_file
2024/06/21 20:55 upstream 66cc544fd75c c2e07261 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in hfs_extend_file
2026/05/14 20:00 linux-next e98d21c170b0 6ccb967e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in hfs_extend_file
2026/02/08 17:39 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 59e4d31a0470 4c131dc4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfs_extend_file
* Struck through repros no longer work on HEAD.