syzbot


possible deadlock in jbd2_journal_lock_updates

Status: upstream: reported C repro on 2023/03/07 17:45
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+163e6a010d5422a65abb@syzkaller.appspotmail.com
First crash: 443d, last: 1h06m
Fix commit to backport (bisect log) :
tree: upstream
commit 62913ae96de747091c4dacd06d158e7729c1a76d
Author: Theodore Ts'o <tytso@mit.edu>
Date: Wed Mar 8 04:15:49 2023 +0000

  ext4, jbd2: add an optimized bmap for the journal inode

  
Bug presence (2)
Date Name Commit Repro Result
2023/05/02 linux-6.1.y (ToT) ca48fc16c493 C [report] possible deadlock in jbd2_journal_lock_updates
2023/05/02 upstream (ToT) 865fdb08197e C Didn't crash
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in jbd2_journal_lock_updates ext4 C error 83148 357d 654d 22/26 fixed on 2023/06/08 14:41
linux-5.15 possible deadlock in jbd2_journal_lock_updates origin:lts-only C inconclusive 37672 3h29m 443d 0/3 upstream: reported C repro on 2023/03/07 17:25
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2023/11/07 10:22 3h35m fix candidate upstream job log (1)

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.1.82-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor239/3541 is trying to acquire lock:
ffff88814bd24170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x2b0/0x380 fs/jbd2/transaction.c:904

but task is already holding lock:
ffff88814bd22b98 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_change_inode_journal_flag+0x1a0/0x6e0 fs/ext4/inode.c:6119

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (&sbi->s_writepages_rwsem){++++}-{0:0}:
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
       percpu_down_write+0x50/0x2f0 kernel/locking/percpu-rwsem.c:227
       ext4_change_inode_journal_flag+0x1a0/0x6e0 fs/ext4/inode.c:6119
       ext4_ioctl_setflags fs/ext4/ioctl.c:688 [inline]
       ext4_fileattr_set+0xe04/0x1770 fs/ext4/ioctl.c:1008
       vfs_fileattr_set+0x8f3/0xd30 fs/ioctl.c:696
       ioctl_setflags fs/ioctl.c:728 [inline]
       do_vfs_ioctl+0x1cd1/0x2a90 fs/ioctl.c:839
       __do_sys_ioctl fs/ioctl.c:868 [inline]
       __se_sys_ioctl+0x81/0x160 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #3 (mapping.invalidate_lock){++++}-{3:3}:
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
       down_write+0x36/0x60 kernel/locking/rwsem.c:1573
       filemap_invalidate_lock include/linux/fs.h:803 [inline]
       ext4_setattr+0xec7/0x1a00 fs/ext4/inode.c:5507
       notify_change+0xce3/0xfc0 fs/attr.c:499
       do_truncate+0x21c/0x300 fs/open.c:65
       do_sys_ftruncate+0x2e2/0x380 fs/open.c:193
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #2 (&sb->s_type->i_mutex_key#8){++++}-{3:3}:
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
       down_read+0xad/0xa30 kernel/locking/rwsem.c:1520
       inode_lock_shared include/linux/fs.h:768 [inline]
       ext4_bmap+0x4b/0x410 fs/ext4/inode.c:3176
       bmap+0xa1/0xd0 fs/inode.c:1842
       jbd2_journal_bmap fs/jbd2/journal.c:977 [inline]
       __jbd2_journal_erase fs/jbd2/journal.c:1794 [inline]
       jbd2_journal_flush+0x5b5/0xc40 fs/jbd2/journal.c:2496
       ext4_ioctl_checkpoint fs/ext4/ioctl.c:1086 [inline]
       __ext4_ioctl fs/ext4/ioctl.c:1594 [inline]
       ext4_ioctl+0x3986/0x5f60 fs/ext4/ioctl.c:1614
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #1 (&journal->j_checkpoint_mutex){+.+.}-{3:3}:
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       mutex_lock_io_nested+0x134/0xab0 kernel/locking/mutex.c:833
       jbd2_journal_flush+0x29b/0xc40 fs/jbd2/journal.c:2468
       ext4_ioctl_checkpoint fs/ext4/ioctl.c:1086 [inline]
       __ext4_ioctl fs/ext4/ioctl.c:1594 [inline]
       ext4_ioctl+0x3986/0x5f60 fs/ext4/ioctl.c:1614
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (&journal->j_barrier){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3090 [inline]
       check_prevs_add kernel/locking/lockdep.c:3209 [inline]
       validate_chain+0x1661/0x5950 kernel/locking/lockdep.c:3825
       __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747
       jbd2_journal_lock_updates+0x2b0/0x380 fs/jbd2/transaction.c:904
       ext4_change_inode_journal_flag+0x1a8/0x6e0 fs/ext4/inode.c:6120
       ext4_ioctl_setflags fs/ext4/ioctl.c:688 [inline]
       ext4_fileattr_set+0xe04/0x1770 fs/ext4/ioctl.c:1008
       vfs_fileattr_set+0x8f3/0xd30 fs/ioctl.c:696
       ioctl_setflags fs/ioctl.c:728 [inline]
       do_vfs_ioctl+0x1cd1/0x2a90 fs/ioctl.c:839
       __do_sys_ioctl fs/ioctl.c:868 [inline]
       __se_sys_ioctl+0x81/0x160 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
       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-executor239/3541:
 #0: ffff88814bd20460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write_file+0x5a/0x1f0 fs/namespace.c:437
 #1: ffff88807398de48 (&sb->s_type->i_mutex_key#8){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
 #1: ffff88807398de48 (&sb->s_type->i_mutex_key#8){++++}-{3:3}, at: vfs_fileattr_set+0x135/0xd30 fs/ioctl.c:681
 #2: ffff88807398dfe8 (mapping.invalidate_lock){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:803 [inline]
 #2: ffff88807398dfe8 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_change_inode_journal_flag+0x115/0x6e0 fs/ext4/inode.c:6111
 #3: ffff88814bd22b98 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_change_inode_journal_flag+0x1a0/0x6e0 fs/ext4/inode.c:6119

stack backtrace:
CPU: 1 PID: 3541 Comm: syz-executor239 Not tainted 6.1.82-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 check_noncircular+0x2fa/0x3b0 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+0x1661/0x5950 kernel/locking/lockdep.c:3825
 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049
 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747
 jbd2_journal_lock_updates+0x2b0/0x380 fs/jbd2/transaction.c:904
 ext4_change_inode_journal_flag+0x1a8/0x6e0 fs/ext4/inode.c:6120
 ext4_ioctl_setflags fs/ext4/ioctl.c:688 [inline]
 ext4_fileattr_set+0xe04/0x1770 fs/ext4/ioctl.c:1008
 vfs_fileattr_set+0x8f3/0xd30 fs/ioctl.c:696
 ioctl_setflags fs/ioctl.c:728 [inline]
 do_vfs_ioctl+0x1cd1/0x2a90 fs/ioctl.c:839
 __do_sys_ioctl fs/ioctl.c:868 [inline]
 __se_sys_ioctl+0x81/0x160 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fdffdbd4369
Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe446a1ee8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0073746e6576652e RCX: 00007fdffdbd4369
RDX: 0000000020000180 RSI: 0000000040086602 RDI: 0000000000000005
RBP: 652e79726f6d656d R08: 00000000000ac5f8 R09: 00000000000ac5f8
R10: 00000000000ac5f8 R11: 0000000000000246 R12: 0000000000000001
R13: 00

Crashes (36692):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/03/26 21:31 linux-6.1.y d7543167affd 454571b6 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/01/10 11:03 linux-6.1.y 38fb82ecd144 b438bd66 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/01/10 10:22 linux-6.1.y 38fb82ecd144 b438bd66 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/01/10 09:59 linux-6.1.y 38fb82ecd144 b438bd66 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2023/10/01 15:59 linux-6.1.y d23900f974e0 8e26a358 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2023/03/15 06:49 linux-6.1.y 6449a0ba6843 0d5c4377 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in jbd2_journal_lock_updates
2023/07/09 14:50 linux-6.1.y 61fd484b2cf6 668cb1fa .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in jbd2_journal_lock_updates
2023/06/23 08:39 linux-6.1.y e84a4e368abe 79782afc .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2023/03/15 04:18 linux-6.1.y 6449a0ba6843 0d5c4377 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in jbd2_journal_lock_updates
2023/03/08 12:32 linux-6.1.y 42616e0f09fb d2b00170 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in jbd2_journal_lock_updates
2024/05/24 02:32 linux-6.1.y 4078fa637fcd 8f98448e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/24 00:35 linux-6.1.y 4078fa637fcd 8f98448e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/23 23:34 linux-6.1.y 4078fa637fcd 8f98448e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/23 22:58 linux-6.1.y 4078fa637fcd 8f98448e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/23 20:42 linux-6.1.y 4078fa637fcd 4c2072ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in jbd2_journal_lock_updates
2024/05/23 17:14 linux-6.1.y 4078fa637fcd 4c2072ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/23 15:33 linux-6.1.y 4078fa637fcd 4c2072ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in jbd2_journal_lock_updates
2024/05/23 10:48 linux-6.1.y 4078fa637fcd 4c2072ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/23 09:42 linux-6.1.y 4078fa637fcd 4c2072ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in jbd2_journal_lock_updates
2024/05/23 08:02 linux-6.1.y 4078fa637fcd 4c2072ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/23 07:05 linux-6.1.y 4078fa637fcd 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/23 03:33 linux-6.1.y 4078fa637fcd 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/23 00:14 linux-6.1.y 4078fa637fcd 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/22 23:11 linux-6.1.y 4078fa637fcd 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/22 20:10 linux-6.1.y 4078fa637fcd 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/22 18:09 linux-6.1.y 4078fa637fcd 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/22 13:09 linux-6.1.y 4078fa637fcd 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/22 12:04 linux-6.1.y 4078fa637fcd 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/22 10:22 linux-6.1.y 4078fa637fcd 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/22 06:37 linux-6.1.y 4078fa637fcd 1014eca7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/22 03:55 linux-6.1.y 4078fa637fcd 1014eca7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/22 02:54 linux-6.1.y 4078fa637fcd 1014eca7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in jbd2_journal_lock_updates
2024/05/22 02:43 linux-6.1.y 4078fa637fcd 1014eca7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/22 00:08 linux-6.1.y 4078fa637fcd 1014eca7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/21 22:49 linux-6.1.y 4078fa637fcd 1014eca7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/21 20:56 linux-6.1.y 4078fa637fcd 4c0d3ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/21 20:51 linux-6.1.y 4078fa637fcd 4c0d3ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/21 15:57 linux-6.1.y 4078fa637fcd 4c0d3ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/21 09:41 linux-6.1.y 4078fa637fcd 4c0d3ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/21 09:14 linux-6.1.y 4078fa637fcd 4c0d3ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/21 07:44 linux-6.1.y 4078fa637fcd 4c0d3ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/21 06:15 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/21 05:51 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/21 03:39 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/21 02:18 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/20 23:48 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/20 23:39 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/20 18:23 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/20 17:21 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/20 16:17 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/20 14:35 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/20 11:59 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
2024/05/22 14:33 linux-6.1.y 4078fa637fcd 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in jbd2_journal_lock_updates
2024/05/21 13:45 linux-6.1.y 4078fa637fcd 4c0d3ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in jbd2_journal_lock_updates
2024/05/21 11:23 linux-6.1.y 4078fa637fcd 4c0d3ee3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in jbd2_journal_lock_updates
2024/05/20 21:47 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in jbd2_journal_lock_updates
2023/03/07 17:44 linux-6.1.y 42616e0f09fb d7ea8bc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf possible deadlock in jbd2_journal_lock_updates
* Struck through repros no longer work on HEAD.