syzbot


possible deadlock in ext4_bmap

Status: fixed on 2023/06/08 14:41
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+9543479984ae9e576000@syzkaller.appspotmail.com
Fix commit: 62913ae96de7 ext4, jbd2: add an optimized bmap for the journal inode
First crash: 624d, last: 320d
Cause bisection: failed (error log, bisect log)
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] possible deadlock in ext4_bmap 3 (5) 2023/04/30 23:28
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in ext4_bmap origin:lts-only C inconclusive 20830 4h39m 413d 0/3 upstream: reported C repro on 2023/03/07 16:42
linux-6.1 possible deadlock in ext4_bmap origin:lts-only C done 20637 6h38m 413d 0/3 upstream: reported C repro on 2023/03/07 17:07
Last patch testing requests (2)
Created Duration User Patch Repo Result
2023/03/09 15:14 18m tytso@mit.edu git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev OK log
2022/08/09 11:10 18m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git ca688bff68bc OK log

Sample crash report:
warning: checkpointing journal with EXT4_IOC_CHECKPOINT_FLAG_ZEROOUT can be slow
======================================================
WARNING: possible circular locking dependency detected
6.2.0-syzkaller-13413-g0a3f9a6b0265 #0 Not tainted
------------------------------------------------------
syz-executor201/5081 is trying to acquire lock:
ffff888144d40400 (&sb->s_type->i_mutex_key#8){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
ffff888144d40400 (&sb->s_type->i_mutex_key#8){++++}-{3:3}, at: ext4_bmap+0x52/0x470 fs/ext4/inode.c:3242

but task is already holding lock:
ffff88802afba3f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x47f/0xc90 fs/jbd2/journal.c:2473

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&journal->j_checkpoint_mutex){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       mutex_lock_io_nested+0x143/0x11a0 kernel/locking/mutex.c:833
       jbd2_journal_flush+0x19e/0xc90 fs/jbd2/journal.c:2463
       ext4_ioctl_checkpoint fs/ext4/ioctl.c:1079 [inline]
       __ext4_ioctl+0xb3f/0x4c90 fs/ext4/ioctl.c:1587
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #2 (&journal->j_barrier){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
       jbd2_journal_lock_updates+0x162/0x310 fs/jbd2/transaction.c:904
       ext4_change_inode_journal_flag+0x188/0x550 fs/ext4/inode.c:6156
       ext4_ioctl_setflags fs/ext4/ioctl.c:684 [inline]
       ext4_fileattr_set+0xe78/0x1a50 fs/ext4/ioctl.c:1001
       vfs_fileattr_set+0x7ff/0xc40 fs/ioctl.c:696
       ioctl_fssetxattr fs/ioctl.c:758 [inline]
       do_vfs_ioctl+0xfa8/0x1670 fs/ioctl.c:845
       __do_sys_ioctl fs/ioctl.c:868 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __x64_sys_ioctl+0x10c/0x210 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #1 (&sbi->s_writepages_rwsem){++++}-{0:0}:
       percpu_down_write+0x53/0x390 kernel/locking/percpu-rwsem.c:227
       ext4_ind_migrate+0x23b/0x860 fs/ext4/migrate.c:624
       ext4_ioctl_setflags fs/ext4/ioctl.c:693 [inline]
       ext4_fileattr_set+0x1582/0x1a50 fs/ext4/ioctl.c:1001
       vfs_fileattr_set+0x7ff/0xc40 fs/ioctl.c:696
       ioctl_fssetxattr fs/ioctl.c:758 [inline]
       do_vfs_ioctl+0xfa8/0x1670 fs/ioctl.c:845
       __do_sys_ioctl fs/ioctl.c:868 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __x64_sys_ioctl+0x10c/0x210 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (&sb->s_type->i_mutex_key#8){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3098 [inline]
       check_prevs_add kernel/locking/lockdep.c:3217 [inline]
       validate_chain kernel/locking/lockdep.c:3832 [inline]
       __lock_acquire+0x2ec7/0x5d40 kernel/locking/lockdep.c:5056
       lock_acquire kernel/locking/lockdep.c:5669 [inline]
       lock_acquire+0x1e3/0x670 kernel/locking/lockdep.c:5634
       down_read+0x3d/0x50 kernel/locking/rwsem.c:1520
       inode_lock_shared include/linux/fs.h:768 [inline]
       ext4_bmap+0x52/0x470 fs/ext4/inode.c:3242
       bmap+0xae/0x120 fs/inode.c:1799
       jbd2_journal_bmap+0xac/0x1c0 fs/jbd2/journal.c:976
       __jbd2_journal_erase fs/jbd2/journal.c:1788 [inline]
       jbd2_journal_flush+0x87b/0xc90 fs/jbd2/journal.c:2491
       ext4_ioctl_checkpoint fs/ext4/ioctl.c:1079 [inline]
       __ext4_ioctl+0xb3f/0x4c90 fs/ext4/ioctl.c:1587
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

other info that might help us debug this:

Chain exists of:
  &sb->s_type->i_mutex_key#8 --> &journal->j_barrier --> &journal->j_checkpoint_mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&journal->j_checkpoint_mutex);
                               lock(&journal->j_barrier);
                               lock(&journal->j_checkpoint_mutex);
  lock(&sb->s_type->i_mutex_key#8);

 *** DEADLOCK ***

2 locks held by syz-executor201/5081:
 #0: ffff88802afba170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x162/0x310 fs/jbd2/transaction.c:904
 #1: ffff88802afba3f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: jbd2_journal_flush+0x47f/0xc90 fs/jbd2/journal.c:2473

stack backtrace:
CPU: 0 PID: 5081 Comm: syz-executor201 Not tainted 6.2.0-syzkaller-13413-g0a3f9a6b0265 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2178
 check_prev_add kernel/locking/lockdep.c:3098 [inline]
 check_prevs_add kernel/locking/lockdep.c:3217 [inline]
 validate_chain kernel/locking/lockdep.c:3832 [inline]
 __lock_acquire+0x2ec7/0x5d40 kernel/locking/lockdep.c:5056
 lock_acquire kernel/locking/lockdep.c:5669 [inline]
 lock_acquire+0x1e3/0x670 kernel/locking/lockdep.c:5634
 down_read+0x3d/0x50 kernel/locking/rwsem.c:1520
 inode_lock_shared include/linux/fs.h:768 [inline]
 ext4_bmap+0x52/0x470 fs/ext4/inode.c:3242
 bmap+0xae/0x120 fs/inode.c:1799
 jbd2_journal_bmap+0xac/0x1c0 fs/jbd2/journal.c:976
 __jbd2_journal_erase fs/jbd2/journal.c:1788 [inline]
 jbd2_journal_flush+0x87b/0xc90 fs/jbd2/journal.c:2491
 ext4_ioctl_checkpoint fs/ext4/ioctl.c:1079 [inline]
 __ext4_ioctl+0xb3f/0x4c90 fs/ext4/ioctl.c:1587
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f1e8229db79
Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffddbcc12e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1e8229db79
RDX: 0000000020000000 RSI: 000000004004662b RDI: 0000000000000004
RBP: 00007f1e82261d20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 00

Crashes (78083):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/03/04 10:16 upstream 0a3f9a6b0265 f8902b57 .config strace log report syz C ci-upstream-kasan-gce-root possible deadlock in ext4_bmap
2023/01/05 01:42 upstream 69b41ac87e4a 1dac8c7a .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_bmap
2022/12/18 21:52 upstream f9ff5644bcc0 05494336 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in ext4_bmap
2022/12/07 08:13 upstream 8ed710da2873 d88f3abb .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_bmap
2022/08/21 13:03 upstream 15b3f48a4339 26a13b38 .config strace log report syz C ci-upstream-kasan-gce-root possible deadlock in ext4_bmap
2023/03/08 06:44 net 37d9df224d1e d2b00170 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in ext4_bmap
2022/12/02 00:32 bpf 01f856ae6d0c e080de16 .config strace log report syz C ci-upstream-bpf-kasan-gce possible deadlock in ext4_bmap
2022/08/24 22:03 bpf 0947ae112108 514514f6 .config strace log report syz C ci-upstream-bpf-kasan-gce possible deadlock in ext4_bmap
2022/08/24 21:50 bpf 0947ae112108 514514f6 .config console log report syz C ci-upstream-bpf-kasan-gce possible deadlock in ext4_bmap
2023/03/08 08:26 net-next 0194b64578e9 d2b00170 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ext4_bmap
2022/08/24 20:42 bpf-next d24433c0f4a3 514514f6 .config strace log report syz C ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2022/08/24 20:23 bpf-next d24433c0f4a3 514514f6 .config console log report syz C ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2022/11/06 17:49 linux-next 0cdb3579f1ee 6d752409 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_bmap
2022/08/08 19:02 linux-next ca688bff68bc 88e3a122 .config strace log report syz C ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_bmap
2023/03/08 08:10 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fe15c26ee26e d2b00170 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_bmap
2023/03/06 03:17 upstream f915322fe014 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in ext4_bmap
2023/03/06 01:59 upstream f915322fe014 f8902b57 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in ext4_bmap
2023/03/06 00:23 upstream f915322fe014 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ext4_bmap
2023/03/05 18:27 upstream b01fe98d34f3 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ext4_bmap
2023/03/05 12:24 upstream b01fe98d34f3 f8902b57 .config console log report info ci-qemu-upstream possible deadlock in ext4_bmap
2023/03/05 23:20 upstream b01fe98d34f3 f8902b57 .config console log report info ci-qemu-upstream-386 possible deadlock in ext4_bmap
2023/03/10 16:54 bpf 0e9b47e8bbf0 5205ef30 .config console log report info ci-upstream-bpf-kasan-gce possible deadlock in ext4_bmap
2023/03/10 01:57 net 67eeadf2f953 f08b59ac .config console log report info ci-upstream-net-this-kasan-gce possible deadlock in ext4_bmap
2023/04/13 17:39 bpf-next d319f344561d 3cfcaa1b .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/13 14:35 bpf-next d319f344561d 3cfcaa1b .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/13 12:20 bpf-next d319f344561d 3cfcaa1b .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/13 06:00 bpf-next 10fd5f70c397 82d5e53e .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/12 23:10 bpf-next 10fd5f70c397 82d5e53e .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/12 21:50 bpf-next 10fd5f70c397 82d5e53e .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/12 20:43 bpf-next 10fd5f70c397 82d5e53e .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/12 13:54 bpf-next 75dcef8d3609 1a1596b6 .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/10 20:08 bpf-next c4d3b488a90b 71147e29 .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/09 18:24 bpf-next 5855b0999de4 71147e29 .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/09 06:31 bpf-next 5855b0999de4 71147e29 .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/09 00:22 bpf-next 5855b0999de4 71147e29 .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/08 17:48 bpf-next 5855b0999de4 71147e29 .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/08 14:07 bpf-next 3ebf5212bf04 71147e29 .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/08 06:44 bpf-next 3ebf5212bf04 71147e29 .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/08 02:10 bpf-next 3ebf5212bf04 71147e29 .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/07 18:00 bpf-next f3f213497797 f7ba566d .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/07 15:09 bpf-next f3f213497797 f7ba566d .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/07 11:45 bpf-next f3f213497797 f7ba566d .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/04/06 19:35 bpf-next 5af607a861d4 08707520 .config console log report info ci-upstream-bpf-next-kasan-gce possible deadlock in ext4_bmap
2023/03/10 07:01 net-next db47fa2e4cbf 5205ef30 .config console log report info ci-upstream-net-kasan-gce possible deadlock in ext4_bmap
2023/03/06 13:01 linux-next dc837c1a5137 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_bmap
2022/08/08 07:09 linux-next ca688bff68bc 88e3a122 .config console log report info ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_bmap
2022/08/08 04:36 linux-next ca688bff68bc 88e3a122 .config console log report info ci-upstream-linux-next-kasan-gce-root possible deadlock in ext4_bmap
2023/06/08 08:12 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 058b3a5a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/05/27 06:35 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 cf184559 .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/05/21 14:52 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 4bce1a3e .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/05/21 03:32 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 4bce1a3e .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/05/20 23:00 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 4bce1a3e .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/05/20 09:09 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 96689200 .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/05/17 02:49 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 11c89444 .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/05/03 16:56 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 48e0a81d .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/05/03 12:21 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 48e0a81d .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/05/03 04:29 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 48e0a81d .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/05/02 21:59 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 48e0a81d .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/05/02 12:19 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 52d40fd2 .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/27 15:33 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 6f5b1cc4 .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/26 12:52 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 7560799c .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/26 08:55 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 7560799c .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/26 07:25 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 7560799c .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/25 23:36 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 65320f8e .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/21 05:39 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 2b32bd34 .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/20 01:37 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 a219f34e .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/15 05:42 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 ec410564 .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/14 04:46 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 3cfcaa1b .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/10 12:45 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 71147e29 .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/10 04:19 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 71147e29 .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/09 10:23 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 71147e29 .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/04/08 12:36 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 950b879b7f02 71147e29 .config console log report info ci-qemu2-riscv64 possible deadlock in ext4_bmap
2023/03/24 14:40 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fe15c26ee26e f94b4a29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in ext4_bmap
* Struck through repros no longer work on HEAD.