syzbot

 sign-in | mailing list | source | docs
🐞 Open [723]
🐞 Fixed [119]
🐞 Invalid [745]
⬇ Missing Backports [75]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

possible deadlock in ext4_map_blocks

Status: upstream: reported C repro on 2023/03/08 04:51
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+5cff006fc9de25d004e9@syzkaller.appspotmail.com
First crash: 797d, last: 15h34m
▶ ▼ Bug presence (2)
Date Name Commit Repro Result
2024/02/10 linux-6.1.y (ToT) f1bb70486c9c C [report] possible deadlock in ext4_map_blocks
2024/02/10 upstream (ToT) 4a7bbe7519b6 C Didn't crash
▶ ▼ Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in ext4_map_blocks (2) ext4 14 116d 161d 0/28 closed as dup on 2024/12/12 23:41
linux-4.19 possible deadlock in ext4_map_blocks ext4 11 806d 943d 0/1 upstream: reported on 2022/10/12 20:37
upstream possible deadlock in ext4_map_blocks ext4 480 730d 952d 0/28 auto-obsoleted due to no activity on 2023/08/11 20:48
linux-5.15 possible deadlock in ext4_map_blocks origin:lts-only C done 483 6d22h 794d 0/3 upstream: reported C repro on 2023/03/11 16:28
▶ ▼ Fix bisection attempts (1)
Created Duration User Patch Repo Result
2024/03/19 16:38 2h28m fix candidate upstream OK (0) job log

Sample crash report:
loop0: detected capacity change from 0 to 1024
EXT4-fs: Warning: mounting with an experimental mount option 'dioread_nolock' for blocksize < PAGE_SIZE
======================================================
WARNING: possible circular locking dependency detected
6.1.134-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor182/5887 is trying to acquire lock:
ffff0000e41670e0 (&ei->i_data_sem/1){+.+.}-{3:3}, at: ext4_double_down_write_data_sem+0x3c/0x4c fs/ext4/move_extent.c:-1

but task is already holding lock:
ffff0000e1bdd2c8 (&ei->i_data_sem/2){++++}-{3:3}, at: ext4_double_down_write_data_sem+0x30/0x4c fs/ext4/move_extent.c:-1

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&ei->i_data_sem/2){++++}-{3:3}:
       down_read+0x64/0x308 kernel/locking/rwsem.c:1520
       ext4_map_blocks+0x2ac/0x1810 fs/ext4/inode.c:603
       ext4_getblk+0x198/0x6e8 fs/ext4/inode.c:889
       ext4_bread+0x3c/0x1b0 fs/ext4/inode.c:945
       ext4_quota_read+0x16c/0x294 fs/ext4/super.c:7126
       read_blk fs/quota/quota_tree.c:61 [inline]
       find_tree_dqentry+0x180/0xc5c fs/quota/quota_tree.c:671
       find_tree_dqentry+0x504/0xc5c fs/quota/quota_tree.c:698
       find_tree_dqentry+0x504/0xc5c fs/quota/quota_tree.c:698
       find_tree_dqentry+0x504/0xc5c fs/quota/quota_tree.c:698
       find_dqentry fs/quota/quota_tree.c:716 [inline]
       qtree_read_dquot+0x460/0x73c fs/quota/quota_tree.c:736
       v2_read_dquot+0xc0/0x11c fs/quota/quota_v2.c:336
       dquot_acquire+0x130/0x5c4 fs/quota/dquot.c:463
       ext4_acquire_dquot+0x270/0x420 fs/ext4/super.c:6798
       dqget+0x660/0xcec fs/quota/dquot.c:988
       __dquot_initialize+0x2c8/0xc04 fs/quota/dquot.c:1517
       dquot_initialize+0x24/0x34 fs/quota/dquot.c:1579
       ext4_process_orphan+0x5c/0x2b8 fs/ext4/orphan.c:329
       ext4_orphan_cleanup+0x974/0x1134 fs/ext4/orphan.c:474
       __ext4_fill_super fs/ext4/super.c:5523 [inline]
       ext4_fill_super+0x6f00/0x73a4 fs/ext4/super.c:5654
       get_tree_bdev+0x360/0x54c fs/super.c:1366
       ext4_get_tree+0x28/0x38 fs/ext4/super.c:5684
       vfs_get_tree+0x90/0x274 fs/super.c:1573
       do_new_mount+0x278/0x8fc fs/namespace.c:3056
       path_mount+0x590/0xe5c fs/namespace.c:3386
       do_mount fs/namespace.c:3399 [inline]
       __do_sys_mount fs/namespace.c:3607 [inline]
       __se_sys_mount fs/namespace.c:3584 [inline]
       __arm64_sys_mount+0x498/0x588 fs/namespace.c:3584
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

-> #2 (&s->s_dquot.dqio_sem){++++}-{3:3}:
       down_read+0x64/0x308 kernel/locking/rwsem.c:1520
       v2_read_dquot+0x50/0x11c fs/quota/quota_v2.c:335
       dquot_acquire+0x130/0x5c4 fs/quota/dquot.c:463
       ext4_acquire_dquot+0x270/0x420 fs/ext4/super.c:6798
       dqget+0x660/0xcec fs/quota/dquot.c:988
       __dquot_initialize+0x344/0xc04 fs/quota/dquot.c:1517
       dquot_initialize+0x24/0x34 fs/quota/dquot.c:1579
       ext4_create+0xb4/0x480 fs/ext4/namei.c:2876
       lookup_open fs/namei.c:3482 [inline]
       open_last_lookups fs/namei.c:3550 [inline]
       path_openat+0xeac/0x2548 fs/namei.c:3780
       do_filp_open+0x1bc/0x3cc fs/namei.c:3810
       do_sys_openat2+0x128/0x3e0 fs/open.c:1318
       do_sys_open fs/open.c:1334 [inline]
       __do_sys_openat fs/open.c:1350 [inline]
       __se_sys_openat fs/open.c:1345 [inline]
       __arm64_sys_openat+0x1f0/0x240 fs/open.c:1345
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

-> #1 (&dquot->dq_lock){+.+.}-{3:3}:
       __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603
       __mutex_lock kernel/locking/mutex.c:747 [inline]
       mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
       dquot_commit+0x54/0x240 fs/quota/dquot.c:507
       ext4_write_dquot+0x1b4/0x314 fs/ext4/super.c:6778
       ext4_mark_dquot_dirty+0xe8/0x140 fs/ext4/super.c:6838
       mark_dquot_dirty fs/quota/dquot.c:372 [inline]
       mark_all_dquot_dirty+0x108/0x424 fs/quota/dquot.c:412
       __dquot_alloc_space+0xb28/0xf50 fs/quota/dquot.c:1752
       dquot_alloc_space_nodirty include/linux/quotaops.h:300 [inline]
       dquot_alloc_space include/linux/quotaops.h:313 [inline]
       swap_inode_boot_loader fs/ext4/ioctl.c:494 [inline]
       __ext4_ioctl fs/ext4/ioctl.c:1424 [inline]
       ext4_ioctl+0x5c7c/0x6b24 fs/ext4/ioctl.c:1614
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

-> #0 (&ei->i_data_sem/1){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3090 [inline]
       check_prevs_add kernel/locking/lockdep.c:3209 [inline]
       validate_chain kernel/locking/lockdep.c:3825 [inline]
       __lock_acquire+0x3338/0x7680 kernel/locking/lockdep.c:5049
       lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5662
       down_write_nested+0x64/0x94 kernel/locking/rwsem.c:1689
       ext4_double_down_write_data_sem+0x3c/0x4c fs/ext4/move_extent.c:-1
       swap_inode_boot_loader fs/ext4/ioctl.c:426 [inline]
       __ext4_ioctl fs/ext4/ioctl.c:1424 [inline]
       ext4_ioctl+0x4e8c/0x6b24 fs/ext4/ioctl.c:1614
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

other info that might help us debug this:

Chain exists of:
  &ei->i_data_sem/1 --> &s->s_dquot.dqio_sem --> &ei->i_data_sem/2

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ei->i_data_sem/2);
                               lock(&s->s_dquot.dqio_sem);
                               lock(&ei->i_data_sem/2);
  lock(&ei->i_data_sem/1);

 *** DEADLOCK ***

5 locks held by syz-executor182/5887:
 #0: ffff0000d99fe460 (sb_writers#3){.+.+}-{0:0}, at: mnt_want_write_file+0x64/0x1e8 fs/namespace.c:437
 #1: ffff0000e1bdd440 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
 #1: ffff0000e1bdd440 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: lock_two_nondirectories+0xd4/0x120 fs/inode.c:1208
 #2: ffff0000e4167258 (&sb->s_type->i_mutex_key#9/4){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
 #2: ffff0000e4167258 (&sb->s_type->i_mutex_key#9/4){+.+.}-{3:3}, at: lock_two_nondirectories+0xc4/0x120 fs/inode.c:1210
 #3: ffff0000e1bdd5e0 (mapping.invalidate_lock){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:803 [inline]
 #3: ffff0000e1bdd5e0 (mapping.invalidate_lock){++++}-{3:3}, at: swap_inode_boot_loader fs/ext4/ioctl.c:402 [inline]
 #3: ffff0000e1bdd5e0 (mapping.invalidate_lock){++++}-{3:3}, at: __ext4_ioctl fs/ext4/ioctl.c:1424 [inline]
 #3: ffff0000e1bdd5e0 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_ioctl+0x4964/0x6b24 fs/ext4/ioctl.c:1614
 #4: ffff0000e1bdd2c8 (&ei->i_data_sem/2){++++}-{3:3}, at: ext4_double_down_write_data_sem+0x30/0x4c fs/ext4/move_extent.c:-1

stack backtrace:
CPU: 0 PID: 5887 Comm: syz-executor182 Not tainted 6.1.134-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call trace:
 dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
 dump_stack+0x1c/0x5c lib/dump_stack.c:113
 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2048
 check_noncircular+0x2cc/0x378 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3090 [inline]
 check_prevs_add kernel/locking/lockdep.c:3209 [inline]
 validate_chain kernel/locking/lockdep.c:3825 [inline]
 __lock_acquire+0x3338/0x7680 kernel/locking/lockdep.c:5049
 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5662
 down_write_nested+0x64/0x94 kernel/locking/rwsem.c:1689
 ext4_double_down_write_data_sem+0x3c/0x4c fs/ext4/move_extent.c:-1
 swap_inode_boot_loader fs/ext4/ioctl.c:426 [inline]
 __ext4_ioctl fs/ext4/ioctl.c:1424 [inline]
 ext4_ioctl+0x4e8c/0x6b24 fs/ext4/ioctl.c:1614
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Crashes (371):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/14 19:03 linux-6.1.y 420102835862 0bd6db41 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1 (corrupt fs)] [mounted in repro #2 (corrupt fs)] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2024/02/10 01:44 linux-6.1.y f1bb70486c9c 77b23aa1 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/05/13 01:48 linux-6.1.y 02b72ccb5f9d f6671af7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/05/12 10:57 linux-6.1.y 02b72ccb5f9d 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/05/07 05:10 linux-6.1.y ac7079a42ea5 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/05/05 13:48 linux-6.1.y ac7079a42ea5 6ca47dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/05/04 14:50 linux-6.1.y b6736e03756f b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/05/01 23:18 linux-6.1.y 535ec20c5027 51b137cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/30 15:23 linux-6.1.y 535ec20c5027 85a5a23f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/30 03:57 linux-6.1.y 535ec20c5027 85a5a23f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/29 13:24 linux-6.1.y 535ec20c5027 aeb6ec69 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/28 01:25 linux-6.1.y 535ec20c5027 c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/26 03:10 linux-6.1.y 535ec20c5027 c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/25 22:33 linux-6.1.y 535ec20c5027 c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/25 08:36 linux-6.1.y 420102835862 e3715315 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/24 11:01 linux-6.1.y 420102835862 9882047a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/23 13:32 linux-6.1.y 420102835862 53a8b9bd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/23 06:51 linux-6.1.y 420102835862 53a8b9bd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/21 03:28 linux-6.1.y 420102835862 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/19 15:57 linux-6.1.y 420102835862 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/18 08:19 linux-6.1.y 420102835862 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/16 22:49 linux-6.1.y 420102835862 a95239b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/11 12:35 linux-6.1.y 420102835862 94486846 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/10 01:28 linux-6.1.y 3dfebb87d7eb 988b336c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/05 05:42 linux-6.1.y 8e60a714ba3b c53ea9c9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/04/01 18:01 linux-6.1.y 8e60a714ba3b b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/03/30 06:09 linux-6.1.y 8e60a714ba3b d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/03/29 11:03 linux-6.1.y 8e60a714ba3b cf25e2c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/03/26 04:55 linux-6.1.y 344a09659766 89d30d73 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/03/25 23:21 linux-6.1.y 344a09659766 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/03/24 02:40 linux-6.1.y 344a09659766 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/03/23 14:43 linux-6.1.y 344a09659766 4e8d3850 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/03/23 08:10 linux-6.1.y 344a09659766 4e8d3850 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/03/23 01:47 linux-6.1.y 344a09659766 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/03/22 05:13 linux-6.1.y 344a09659766 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/03/21 23:12 linux-6.1.y 344a09659766 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in ext4_map_blocks
2025/05/13 00:31 linux-6.1.y 02b72ccb5f9d f6671af7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/05/09 22:07 linux-6.1.y 02b72ccb5f9d 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/05/09 09:53 linux-6.1.y 02b72ccb5f9d bb813bcc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/05/09 04:34 linux-6.1.y ac7079a42ea5 bb813bcc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/05/06 19:56 linux-6.1.y ac7079a42ea5 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/05/04 08:02 linux-6.1.y b6736e03756f b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/05/03 20:11 linux-6.1.y b6736e03756f b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/05/02 09:26 linux-6.1.y b6736e03756f d7f099d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/04/27 02:37 linux-6.1.y 535ec20c5027 c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/04/24 08:02 linux-6.1.y 420102835862 9882047a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/04/19 20:26 linux-6.1.y 420102835862 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/04/12 12:39 linux-6.1.y 420102835862 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/04/11 21:33 linux-6.1.y 420102835862 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/04/08 17:00 linux-6.1.y 3dfebb87d7eb a775275d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/03/28 14:43 linux-6.1.y 344a09659766 6c09fb82 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/03/24 07:39 linux-6.1.y 344a09659766 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2025/03/19 23:22 linux-6.1.y 344a09659766 e20d7b13 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
2023/03/08 04:51 linux-6.1.y 42616e0f09fb d2b00170 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in ext4_map_blocks
* Struck through repros no longer work on HEAD.