syzbot


possible deadlock in hfsplus_block_allocate

Status: upstream: reported C repro on 2022/11/29 13:38
Subsystems: hfs
[Documentation on labels]
Reported-by: syzbot+b6ccd31787585244a855@syzkaller.appspotmail.com
First crash: 1122d, last: 9h07m
Cause bisection: introduced by (bisect log) :
commit 427c76aed29ec12a57f11546a5036df3cc52855e
Author: Sean Christopherson <seanjc@google.com>
Date: Sat Jul 29 01:35:32 2023 +0000

  KVM: x86/mmu: Bug the VM if write-tracking is used but not enabled

Crash: possible deadlock in hfsplus_block_allocate (log)
Repro: C syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] possible deadlock in hfsplus_block_allocate 0 (3) 2024/03/14 08:20
Similar bugs (8)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in hfsplus_block_allocate 4 26 605d 1001d 0/3 auto-obsoleted due to no activity on 2024/08/08 03:24
linux-4.14 possible deadlock in hfsplus_block_allocate hfsplus 4 2 1072d 1089d 0/1 upstream: reported on 2023/01/02 02:59
linux-6.1 possible deadlock in hfsplus_block_allocate (2) origin:upstream 4 C error 10 37d 383d 0/3 upstream: reported C repro on 2024/12/07 22:33
linux-5.15 possible deadlock in hfsplus_block_allocate (3) origin:upstream 4 C error 4 2d21h 345d 0/3 upstream: reported C repro on 2025/01/14 13:47
linux-5.15 possible deadlock in hfsplus_block_allocate (2) 4 1 509d 509d 0/3 auto-obsoleted due to no activity on 2024/11/11 18:00
linux-6.6 possible deadlock in hfsplus_block_allocate 4 1 48d 48d 0/2 upstream: reported on 2025/11/08 05:29
linux-4.19 possible deadlock in hfsplus_block_allocate hfsplus 4 2 1092d 1099d 0/1 upstream: reported on 2022/12/22 13:15
linux-5.15 possible deadlock in hfsplus_block_allocate 4 18 647d 1007d 0/3 auto-obsoleted due to no activity on 2024/06/27 07:36
Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/09/10 13:16 20m retest repro upstream report log
2025/09/10 13:16 35m retest repro upstream report log
2025/08/27 10:56 19m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2025/08/27 10:56 20m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2025/08/12 12:05 14m retest repro upstream report log
2025/08/12 12:05 42m retest repro upstream report log
2025/08/12 12:05 15m retest repro upstream report log
2025/06/15 12:26 47m retest repro upstream report log
2025/04/06 23:14 1h06m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2025/04/06 23:14 50m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.27/6089 is trying to acquire lock:
ffff888033d3d0f8 (&sbi->alloc_mutex){+.+.}-{4:4}, at: hfsplus_block_allocate+0xd2/0xd10 fs/hfsplus/bitmap.c:35

but task is already holding lock:
ffff88807bf93dc8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1ca/0x1320 fs/hfsplus/extents.c:453

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:614 [inline]
       __mutex_lock+0x1aa/0x1ca0 kernel/locking/mutex.c:776
       hfsplus_get_block+0x272/0xac0 fs/hfsplus/extents.c:260
       block_read_full_folio+0x457/0x850 fs/buffer.c:2420
       filemap_read_folio+0xc8/0x2a0 mm/filemap.c:2496
       do_read_cache_folio+0x266/0x5c0 mm/filemap.c:4096
       do_read_cache_page mm/filemap.c:4162 [inline]
       read_cache_page+0x5b/0x160 mm/filemap.c:4171
       read_mapping_page include/linux/pagemap.h:1011 [inline]
       hfsplus_block_allocate+0x131/0xd10 fs/hfsplus/bitmap.c:37
       hfsplus_file_extend+0x459/0x1320 fs/hfsplus/extents.c:464
       hfsplus_get_block+0x1a9/0xac0 fs/hfsplus/extents.c:245
       __block_write_begin_int+0x4f4/0x16d0 fs/buffer.c:2145
       block_write_begin+0x9d/0x1d0 fs/buffer.c:2256
       cont_write_begin+0x61a/0x950 fs/buffer.c:2594
       hfsplus_write_begin+0x64/0x120 fs/hfsplus/inode.c:48
       cont_expand_zero fs/buffer.c:2555 [inline]
       cont_write_begin+0x6ff/0x950 fs/buffer.c:2584
       hfsplus_write_begin+0x64/0x120 fs/hfsplus/inode.c:48
       generic_cont_expand_simple+0x122/0x200 fs/buffer.c:2485
       hfsplus_setattr+0x250/0x320 fs/hfsplus/inode.c:280
       notify_change+0x6d2/0x1290 fs/attr.c:546
       do_truncate+0x1d7/0x230 fs/open.c:68
       do_ftruncate+0x59e/0x920 fs/open.c:195
       do_sys_ftruncate+0x61/0xb0 fs/open.c:207
       __do_sys_ftruncate fs/open.c:212 [inline]
       __se_sys_ftruncate fs/open.c:210 [inline]
       __x64_sys_ftruncate+0x58/0x80 fs/open.c:210
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&sbi->alloc_mutex){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain kernel/locking/lockdep.c:3908 [inline]
       __lock_acquire+0x1669/0x2890 kernel/locking/lockdep.c:5237
       lock_acquire kernel/locking/lockdep.c:5868 [inline]
       lock_acquire+0x179/0x330 kernel/locking/lockdep.c:5825
       __mutex_lock_common kernel/locking/mutex.c:614 [inline]
       __mutex_lock+0x1aa/0x1ca0 kernel/locking/mutex.c:776
       hfsplus_block_allocate+0xd2/0xd10 fs/hfsplus/bitmap.c:35
       hfsplus_file_extend+0x459/0x1320 fs/hfsplus/extents.c:464
       hfsplus_get_block+0x1a9/0xac0 fs/hfsplus/extents.c:245
       __block_write_begin_int+0x4f4/0x16d0 fs/buffer.c:2145
       block_write_begin+0x9d/0x1d0 fs/buffer.c:2256
       cont_write_begin+0x61a/0x950 fs/buffer.c:2594
       hfsplus_write_begin+0x64/0x120 fs/hfsplus/inode.c:48
       cont_expand_zero fs/buffer.c:2522 [inline]
       cont_write_begin+0x34f/0x950 fs/buffer.c:2584
       hfsplus_write_begin+0x64/0x120 fs/hfsplus/inode.c:48
       generic_perform_write+0x3c4/0x900 mm/filemap.c:4314
       __generic_file_write_iter+0x1f7/0x240 mm/filemap.c:4431
       generic_file_write_iter+0xe1/0x3d0 mm/filemap.c:4457
       do_iter_readv_writev+0x662/0x9e0 fs/read_write.c:827
       vfs_writev+0x35f/0xde0 fs/read_write.c:1057
       do_pwritev+0x1a6/0x270 fs/read_write.c:1153
       __do_sys_pwritev2 fs/read_write.c:1211 [inline]
       __se_sys_pwritev2 fs/read_write.c:1202 [inline]
       __x64_sys_pwritev2+0xef/0x160 fs/read_write.c:1202
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&HFSPLUS_I(inode)->extents_lock);
                               lock(&sbi->alloc_mutex);
                               lock(&HFSPLUS_I(inode)->extents_lock);
  lock(&sbi->alloc_mutex);

 *** DEADLOCK ***

3 locks held by syz.0.27/6089:
 #0: ffff88807bdde420 (sb_writers#12){.+.+}-{0:0}, at: do_pwritev+0x1a6/0x270 fs/read_write.c:1153
 #1: ffff88807bf93fb8 (&sb->s_type->i_mutex_key#24){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1027 [inline]
 #1: ffff88807bf93fb8 (&sb->s_type->i_mutex_key#24){+.+.}-{4:4}, at: generic_file_write_iter+0x8c/0x3d0 mm/filemap.c:4454
 #2: ffff88807bf93dc8 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{4:4}, at: hfsplus_file_extend+0x1ca/0x1320 fs/hfsplus/extents.c:453

stack backtrace:
CPU: 1 UID: 0 PID: 6089 Comm: syz.0.27 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 print_circular_bug+0x275/0x340 kernel/locking/lockdep.c:2043
 check_noncircular+0x146/0x160 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3165 [inline]
 check_prevs_add kernel/locking/lockdep.c:3284 [inline]
 validate_chain kernel/locking/lockdep.c:3908 [inline]
 __lock_acquire+0x1669/0x2890 kernel/locking/lockdep.c:5237
 lock_acquire kernel/locking/lockdep.c:5868 [inline]
 lock_acquire+0x179/0x330 kernel/locking/lockdep.c:5825
 __mutex_lock_common kernel/locking/mutex.c:614 [inline]
 __mutex_lock+0x1aa/0x1ca0 kernel/locking/mutex.c:776
 hfsplus_block_allocate+0xd2/0xd10 fs/hfsplus/bitmap.c:35
 hfsplus_file_extend+0x459/0x1320 fs/hfsplus/extents.c:464
 hfsplus_get_block+0x1a9/0xac0 fs/hfsplus/extents.c:245
 __block_write_begin_int+0x4f4/0x16d0 fs/buffer.c:2145
 block_write_begin+0x9d/0x1d0 fs/buffer.c:2256
 cont_write_begin+0x61a/0x950 fs/buffer.c:2594
 hfsplus_write_begin+0x64/0x120 fs/hfsplus/inode.c:48
 cont_expand_zero fs/buffer.c:2522 [inline]
 cont_write_begin+0x34f/0x950 fs/buffer.c:2584
 hfsplus_write_begin+0x64/0x120 fs/hfsplus/inode.c:48
 generic_perform_write+0x3c4/0x900 mm/filemap.c:4314
 __generic_file_write_iter+0x1f7/0x240 mm/filemap.c:4431
 generic_file_write_iter+0xe1/0x3d0 mm/filemap.c:4457
 do_iter_readv_writev+0x662/0x9e0 fs/read_write.c:827
 vfs_writev+0x35f/0xde0 fs/read_write.c:1057
 do_pwritev+0x1a6/0x270 fs/read_write.c:1153
 __do_sys_pwritev2 fs/read_write.c:1211 [inline]
 __se_sys_pwritev2 fs/read_write.c:1202 [inline]
 __x64_sys_pwritev2+0xef/0x160 fs/read_write.c:1202
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd41798f749
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:00007fff859fa628 EFLAGS: 00000246 ORIG_RAX: 0000000000000148
RAX: ffffffffffffffda RBX: 00007fd417be5fa0 RCX: 00007fd41798f749
RDX: 0000000000000001 RSI: 00002000000001c0 RDI: 0000000000000005
RBP: 00007fd417a13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000007fff R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd417be5fa0 R14: 00007fd417be5fa0 R15: 0000000000000006
 </TASK>

Crashes (385):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/26 02:10 upstream ccd1cdca5cd4 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-upstream-kasan-badwrites-root possible deadlock in hfsplus_block_allocate
2025/10/13 07:17 upstream 3a8660878839 ff1712fe .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 hfsplus_block_allocate
2025/07/28 18:02 upstream 038d61fd6422 6654ea9c .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 hfsplus_block_allocate
2025/07/13 16:16 upstream 3f31a806a62e 3cda49cf .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-upstream-kasan-gce-root possible deadlock in hfsplus_block_allocate
2025/05/11 05:06 upstream bec6f00f120e 77908e5f .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-upstream-kasan-gce-root possible deadlock in hfsplus_block_allocate
2024/11/14 08:37 upstream 0a9b9d17f3a7 a8c99394 .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 hfsplus_block_allocate
2024/06/23 16:33 upstream 5f583a3162ff 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 hfsplus_block_allocate
2025/01/06 07:36 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 573067a5a685 f3558dbf .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 hfsplus_block_allocate
2024/12/01 17:59 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7b1d1d4cfac0 68914665 .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 hfsplus_block_allocate
2024/03/13 22:36 upstream 61387b8dcf1d f919f202 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs possible deadlock in hfsplus_block_allocate
2025/12/25 01:32 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfsplus_block_allocate
2025/12/21 11:48 upstream 9094662f6707 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfsplus_block_allocate
2025/12/14 23:30 upstream 8f0b4cce4481 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfsplus_block_allocate
2025/12/07 05:10 upstream cc3ee4ba57b7 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfsplus_block_allocate
2025/12/02 20:16 upstream 4a26e7032d7d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfsplus_block_allocate
2025/12/01 03:49 upstream e69c7c175115 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfsplus_block_allocate
2025/11/29 14:04 upstream 19eef1d98eed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfsplus_block_allocate
2025/11/26 19:00 upstream 30f09200cc4a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfsplus_block_allocate
2025/11/24 02:17 upstream d0e88704d96c 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfsplus_block_allocate
2025/11/21 23:43 upstream fd95357fd8c6 c31c1b0b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in hfsplus_block_allocate
2025/10/29 06:46 upstream 8eefed8f65cc fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfsplus_block_allocate
2025/10/25 13:10 upstream 566771afc7a8 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in hfsplus_block_allocate
2025/10/15 12:24 upstream 9b332cece987 b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in hfsplus_block_allocate
2025/07/29 05:46 upstream ced1b9e0392d c4a95487 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfsplus_block_allocate
2025/07/28 17:14 upstream 038d61fd6422 c4a95487 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfsplus_block_allocate
2025/07/27 13:37 upstream ec2df4364666 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in hfsplus_block_allocate
2025/07/27 12:15 upstream ec2df4364666 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in hfsplus_block_allocate
2025/07/27 12:14 upstream ec2df4364666 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in hfsplus_block_allocate
2025/07/16 12:59 upstream 155a3c003e55 c118d736 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in hfsplus_block_allocate
2025/07/16 09:54 upstream 155a3c003e55 124ec9cc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in hfsplus_block_allocate
2024/05/01 05:54 upstream 50dffbf77180 9e0e6af1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in hfsplus_block_allocate
2024/05/01 02:06 upstream 50dffbf77180 9e0e6af1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in hfsplus_block_allocate
2025/11/24 04:02 upstream d0e88704d96c 4fb8ef37 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfsplus_block_allocate
2025/11/09 02:44 upstream 7bb4d6512545 4e1406b4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfsplus_block_allocate
2025/11/09 02:44 upstream 7bb4d6512545 4e1406b4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfsplus_block_allocate
2025/11/03 03:12 upstream 6146a0f1dfae 2c50b6a9 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfsplus_block_allocate
2025/10/22 22:41 upstream dd72c8fcf6d3 c0460fcd .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfsplus_block_allocate
2025/10/20 17:28 upstream 211ddde0823f d422939c .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfsplus_block_allocate
2025/10/11 07:04 upstream 917167ed1211 ff1712fe .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfsplus_block_allocate
2025/09/30 00:22 upstream 449c2b302c8e 86341da6 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfsplus_block_allocate
2025/09/16 09:22 upstream 46a51f4f5eda e2beed91 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfsplus_block_allocate
2025/07/26 01:11 upstream 2942242dde89 fb8f743d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in hfsplus_block_allocate
2024/04/30 11:22 upstream 98369dccd2f8 3cb29304 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in hfsplus_block_allocate
2024/04/22 01:33 upstream 3b68086599f8 af24b050 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in hfsplus_block_allocate
2025/12/14 12:13 linux-next d9771d0dbe18 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in hfsplus_block_allocate
2025/12/05 02:32 linux-next bc04acf4aeca d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in hfsplus_block_allocate
2025/10/26 00:59 linux-next 72fb0170ef1f c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in hfsplus_block_allocate
2025/10/13 05:12 linux-next 2b763d465239 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in hfsplus_block_allocate
2025/09/29 08:25 linux-next 262858079afd 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in hfsplus_block_allocate
2025/12/25 06:56 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8f0b4cce4481 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/12/21 03:53 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8f0b4cce4481 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/12/13 16:51 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 05c93f3395ed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/12/11 03:16 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 05c93f3395ed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/11/22 07:16 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 3812f8fa7c83 c31c1b0b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/11/10 23:43 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e424ed997df8 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/11/10 01:47 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e424ed997df8 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/11/09 19:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e424ed997df8 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/11/05 09:35 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci dcb6fa37fd7b a6c9c731 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/11/01 14:35 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci dcb6fa37fd7b 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/10/30 05:27 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci b98c94eed4a9 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/10/28 09:51 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci b98c94eed4a9 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/10/28 05:19 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci b98c94eed4a9 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/09/19 07:11 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci c9d61056440c e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2025/09/18 18:23 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 6edf2885ebeb e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
2022/11/29 13:13 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 6d464646530f 05dc7993 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in hfsplus_block_allocate
* Struck through repros no longer work on HEAD.