syzbot


possible deadlock in jbd2_journal_lock_updates

Status: upstream: reported C repro on 2022/08/08 07:34
Reported-by: syzbot+79e6bbabf3ce17357969@syzkaller.appspotmail.com
First crash: 178d, last: now

Cause bisection: failed (bisect log)
Last patch testing requests:
Created Duration User Patch Repo Result
2022/08/21 02:36 18m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git ca688bff68bc OK log
2022/08/19 12:20 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: possible circular locking dependency detected
6.2.0-rc3-syzkaller-00008-g1fe4fd6f5cad #0 Not tainted
------------------------------------------------------
syz-executor702/5055 is trying to acquire lock:
ffff88814b99c170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x162/0x310 fs/jbd2/transaction.c:904

but task is already holding lock:
ffff888029ef2b98 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_change_inode_journal_flag+0x180/0x550 fs/ext4/inode.c:6157

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (&sbi->s_writepages_rwsem){++++}-{0:0}:
       percpu_down_write+0x53/0x390 kernel/locking/percpu-rwsem.c:227
       ext4_change_inode_journal_flag+0x180/0x550 fs/ext4/inode.c:6157
       ext4_ioctl_setflags fs/ext4/ioctl.c:687 [inline]
       ext4_fileattr_set+0xe78/0x1a50 fs/ext4/ioctl.c:1004
       vfs_fileattr_set+0x7f9/0xbe0 fs/ioctl.c:696
       ioctl_fssetxattr fs/ioctl.c:758 [inline]
       do_vfs_ioctl+0xf8d/0x15b0 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

-> #3 (mapping.invalidate_lock){++++}-{3:3}:
       down_write+0x94/0x220 kernel/locking/rwsem.c:1562
       filemap_invalidate_lock include/linux/fs.h:801 [inline]
       ext4_setattr+0x75a/0x2be0 fs/ext4/inode.c:5545
       notify_change+0xca7/0x1420 fs/attr.c:482
       do_truncate+0x143/0x200 fs/open.c:65
       do_sys_ftruncate+0x51f/0x710 fs/open.c:193
       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 (&sb->s_type->i_mutex_key#7){++++}-{3:3}:
       down_read+0x9c/0x450 kernel/locking/rwsem.c:1509
       inode_lock_shared include/linux/fs.h:766 [inline]
       ext4_bmap+0x52/0x470 fs/ext4/inode.c:3243
       bmap+0xae/0x120 fs/inode.c:1798
       jbd2_journal_bmap+0xac/0x180 fs/jbd2/journal.c:977
       __jbd2_journal_erase fs/jbd2/journal.c:1789 [inline]
       jbd2_journal_flush+0x853/0xc00 fs/jbd2/journal.c:2492
       ext4_ioctl_checkpoint fs/ext4/ioctl.c:1082 [inline]
       __ext4_ioctl+0xb01/0x4b60 fs/ext4/ioctl.c:1590
       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

-> #1 (&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/0xc00 fs/jbd2/journal.c:2464
       ext4_ioctl_checkpoint fs/ext4/ioctl.c:1082 [inline]
       __ext4_ioctl+0xb01/0x4b60 fs/ext4/ioctl.c:1590
       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

-> #0 (&journal->j_barrier){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3097 [inline]
       check_prevs_add kernel/locking/lockdep.c:3216 [inline]
       validate_chain kernel/locking/lockdep.c:3831 [inline]
       __lock_acquire+0x2a43/0x56d0 kernel/locking/lockdep.c:5055
       lock_acquire kernel/locking/lockdep.c:5668 [inline]
       lock_acquire+0x1e3/0x630 kernel/locking/lockdep.c:5633
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12f/0x1360 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:6158
       ext4_ioctl_setflags fs/ext4/ioctl.c:687 [inline]
       ext4_fileattr_set+0xe78/0x1a50 fs/ext4/ioctl.c:1004
       vfs_fileattr_set+0x7f9/0xbe0 fs/ioctl.c:696
       ioctl_fssetxattr fs/ioctl.c:758 [inline]
       do_vfs_ioctl+0xf8d/0x15b0 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

other info that might help us debug this:

Chain exists of:
  &journal->j_barrier --> mapping.invalidate_lock --> &sbi->s_writepages_rwsem

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&sbi->s_writepages_rwsem);
                               lock(mapping.invalidate_lock);
                               lock(&sbi->s_writepages_rwsem);
  lock(&journal->j_barrier);

 *** DEADLOCK ***

4 locks held by syz-executor702/5055:
 #0: ffff888029eba460 (sb_writers#5){.+.+}-{0:0}, at: ioctl_setflags fs/ioctl.c:725 [inline]
 #0: ffff888029eba460 (sb_writers#5){.+.+}-{0:0}, at: do_vfs_ioctl+0xf52/0x15b0 fs/ioctl.c:839
 #1: ffff88806fa364c0 (&sb->s_type->i_mutex_key#7){++++}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
 #1: ffff88806fa364c0 (&sb->s_type->i_mutex_key#7){++++}-{3:3}, at: vfs_fileattr_set+0x14c/0xbe0 fs/ioctl.c:681
 #2: ffff88806fa36660 (mapping.invalidate_lock){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
 #2: ffff88806fa36660 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_change_inode_journal_flag+0x127/0x550 fs/ext4/inode.c:6149
 #3: ffff888029ef2b98 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_change_inode_journal_flag+0x180/0x550 fs/ext4/inode.c:6157

stack backtrace:
CPU: 1 PID: 5055 Comm: syz-executor702 Not tainted 6.2.0-rc3-syzkaller-00008-g1fe4fd6f5cad #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106
 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2177
 check_prev_add kernel/locking/lockdep.c:3097 [inline]
 check_prevs_add kernel/locking/lockdep.c:3216 [inline]
 validate_chain kernel/locking/lockdep.c:3831 [inline]
 __lock_acquire+0x2a43/0x56d0 kernel/locking/lockdep.c:5055
 lock_acquire kernel/locking/lockdep.c:5668 [inline]
 lock_acquire+0x1e3/0x630 kernel/locking/lockdep.c:5633
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x12f/0x1360 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:6158
 ext4_ioctl_setflags fs/ext4/ioctl.c:687 [inline]
 ext4_fileattr_set+0xe78/0x1a50 fs/ext4/ioctl.c:1004
 vfs_fileattr_set+0x7f9/0xbe0 fs/ioctl.c:696
 ioctl_fssetxattr fs/ioctl.c:758 [inline]
 do_vfs_ioctl+0xf8d/0x15b0 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
RIP: 0033:0x7f070a643be9
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:00007ffff55c0628 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f070a643be9
RDX: 0000000020000080 RSI: 0000000040086602 RDI: 0000000000000004
RBP: 00007f070a607d90 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f07

Crashes (64385):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci-upstream-kasan-gce-selinux-root 2023/01/09 21:56 upstream 1fe4fd6f5cad 1dac8c7a .config strace log report syz C [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-kasan-gce-selinux-root 2022/12/07 06:33 upstream 8ed710da2873 d88f3abb .config strace log report syz C [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-kasan-gce-smack-root 2022/11/26 15:35 upstream 0b1dcc2cf55a 74a66371 .config strace log report syz C [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-kasan-gce-root 2022/09/25 02:57 upstream 1a61b828566f 0042f2b4 .config strace log report syz C [disk image] [vmlinux] possible deadlock in jbd2_journal_lock_updates
ci-upstream-kasan-gce-root 2022/08/21 11:39 upstream 15b3f48a4339 26a13b38 .config strace log report syz C possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2022/08/24 19:13 bpf 0947ae112108 514514f6 .config strace log report syz C possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-next-kasan-gce 2022/08/24 18:08 bpf-next d24433c0f4a3 514514f6 .config strace log report syz C possible deadlock in jbd2_journal_lock_updates
ci-upstream-linux-next-kasan-gce-root 2022/08/08 16:37 linux-next ca688bff68bc 88e3a122 .config strace log report syz C possible deadlock in jbd2_journal_lock_updates
ci2-upstream-fs 2023/02/02 14:44 upstream 9f266ccaa2f5 16d19e30 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci2-upstream-fs 2023/02/02 13:48 upstream 9f266ccaa2f5 16d19e30 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-kasan-gce-smack-root 2023/02/02 08:23 upstream 9f266ccaa2f5 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-kasan-gce-smack-root 2023/02/02 05:10 upstream 9f266ccaa2f5 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-qemu-upstream 2023/02/02 03:05 upstream 9f266ccaa2f5 7374c4e5 .config console log report info possible deadlock in jbd2_journal_lock_updates
ci2-upstream-fs 2023/02/02 00:59 upstream c0b67534c95c 9a6f477c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-kasan-gce-selinux-root 2023/02/01 20:34 upstream c0b67534c95c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-kasan-gce-smack-root 2023/02/01 17:35 upstream c0b67534c95c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-kasan-gce-smack-root 2023/02/01 16:14 upstream c0b67534c95c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-kasan-gce-root 2023/02/01 15:40 upstream c0b67534c95c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci2-upstream-fs 2023/02/01 05:54 upstream c0b67534c95c b68fb8d6 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-kasan-gce-root 2023/02/01 05:14 upstream 58706f7fb045 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-qemu-upstream 2023/02/01 03:40 upstream 58706f7fb045 7374c4e5 .config console log report info possible deadlock in jbd2_journal_lock_updates
ci-upstream-kasan-gce-root 2023/02/01 02:59 upstream 58706f7fb045 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-qemu-upstream-386 2023/02/01 00:17 upstream 58706f7fb045 7374c4e5 .config console log report info possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/02 12:44 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-this-kasan-gce 2023/02/02 12:43 net 99f1c46011cc 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/02 11:08 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/02 10:08 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/02 08:34 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-this-kasan-gce 2023/02/02 07:18 net 64466c407a73 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/02 06:58 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-this-kasan-gce 2023/02/02 04:34 net 64466c407a73 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/02 02:05 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/02 01:59 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-this-kasan-gce 2023/02/01 23:38 net 64466c407a73 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/01 23:26 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-this-kasan-gce 2023/02/01 22:26 net 64466c407a73 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/01 19:31 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/01 18:40 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/01 16:54 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/01 14:42 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-kasan-gce 2023/02/01 12:38 bpf a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-this-kasan-gce 2023/02/01 09:19 net 8f35ae17ef56 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-this-kasan-gce 2023/02/01 08:15 net 8f35ae17ef56 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-this-kasan-gce 2023/02/01 07:14 net 8f35ae17ef56 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-this-kasan-gce 2023/02/01 07:10 net 8f35ae17ef56 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-kasan-gce 2023/02/02 11:41 net-next 609aa68d6096 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-kasan-gce 2023/02/02 09:24 net-next 609aa68d6096 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-next-kasan-gce 2023/02/02 05:57 bpf-next 10d1b0e4dacc 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-kasan-gce 2023/02/02 04:20 net-next dd25cfab16e6 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-next-kasan-gce 2023/02/02 03:17 bpf-next 10d1b0e4dacc 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-next-kasan-gce 2023/02/02 00:40 bpf-next 10d1b0e4dacc 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-next-kasan-gce 2023/02/01 21:58 bpf-next c1a3daf7363b 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-kasan-gce 2023/02/01 20:57 net-next dd25cfab16e6 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-next-kasan-gce 2023/02/01 14:38 bpf-next c1a3daf7363b 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-next-kasan-gce 2023/02/01 13:37 bpf-next c1a3daf7363b 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-next-kasan-gce 2023/02/01 11:10 bpf-next c1a3daf7363b 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-kasan-gce 2023/02/01 10:14 net-next df54fde451db 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-bpf-next-kasan-gce 2023/02/01 08:24 bpf-next c1a3daf7363b 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-net-kasan-gce 2023/02/01 04:44 net-next df54fde451db 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-linux-next-kasan-gce-root 2023/02/01 11:53 linux-next 66eee64b2354 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
ci-upstream-linux-next-kasan-gce-root 2022/08/08 07:31 linux-next ca688bff68bc 88e3a122 .config console log report info possible deadlock in jbd2_journal_lock_updates
ci-upstream-linux-next-kasan-gce-root 2022/08/08 05:07 linux-next ca688bff68bc 88e3a122 .config console log report info possible deadlock in jbd2_journal_lock_updates
ci-upstream-gce-arm64 2023/01/31 05:36 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci c62c88e05937 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in jbd2_journal_lock_updates
* Struck through repros no longer work on HEAD.