syzbot


possible deadlock in do_journal_begin_r

Status: auto-obsoleted due to no activity on 2024/05/26 14:27
Subsystems: reiserfs
[Documentation on labels]
Reported-by: syzbot+5e385bfa7d505b075d9f@syzkaller.appspotmail.com
First crash: 853d, last: 373d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: failed (error log, bisect log)
  
Discussions (2)
Title Replies (including bot) Last reply
[syzbot] Monthly reiserfs report (May 2023) 0 (1) 2023/05/29 08:47
[syzbot] possible deadlock in do_journal_begin_r 0 (1) 2022/10/01 13:48
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 possible deadlock in do_journal_begin_r reiserfs C error 45 768d 853d 0/1 upstream: reported C repro on 2022/09/27 10:45
linux-4.14 possible deadlock in do_journal_begin_r reiserfs C 55 695d 845d 0/1 upstream: reported C repro on 2022/10/05 14:07
linux-6.1 possible deadlock in do_journal_begin_r origin:upstream missing-backport C done 28 20d 582d 0/3 upstream: reported C repro on 2023/06/25 10:36
linux-5.15 possible deadlock in do_journal_begin_r origin:upstream missing-backport C error 50 9d05h 588d 0/3 upstream: reported C repro on 2023/06/19 07:49
Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/05/26 14:07 18m retest repro upstream OK log
2024/05/26 13:27 21m retest repro upstream OK log
2024/05/26 13:27 17m retest repro upstream OK log
2024/05/26 12:44 20m retest repro upstream OK log
2024/05/26 12:44 17m retest repro upstream OK log
2024/05/09 17:08 20m retest repro upstream OK log
2024/03/17 11:54 19m retest repro upstream error
2024/03/17 11:54 18m retest repro upstream error
2024/03/17 11:54 19m retest repro upstream error
2024/03/17 11:54 18m retest repro upstream error
Fix bisection attempts (8)
Created Duration User Patch Repo Result
2024/02/29 14:10 2h47m bisect fix upstream error job log
2023/10/02 18:46 1h17m bisect fix upstream OK (0) job log log
2023/08/01 15:45 1h31m bisect fix upstream OK (0) job log log
2023/06/24 15:42 44m bisect fix upstream OK (0) job log log
2023/05/02 07:34 44m bisect fix upstream OK (0) job log log
2023/04/02 01:55 39m bisect fix upstream OK (0) job log log
2023/03/03 00:42 42m bisect fix upstream OK (0) job log log
2023/01/31 14:24 27m bisect fix upstream OK (0) job log log

Sample crash report:
REISERFS (device loop0): checking transaction log (loop0)
REISERFS (device loop0): Using tea hash to sort names
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
======================================================
WARNING: possible circular locking dependency detected
6.6.0-rc7-syzkaller-00151-g56567a20b22b #0 Not tainted
------------------------------------------------------
syz-executor363/5030 is trying to acquire lock:
ffffc900043210f0 (&journal->j_mutex){+.+.}-{3:3}, at: reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:813 [inline]
ffffc900043210f0 (&journal->j_mutex){+.+.}-{3:3}, at: lock_journal fs/reiserfs/journal.c:534 [inline]
ffffc900043210f0 (&journal->j_mutex){+.+.}-{3:3}, at: do_journal_begin_r+0x352/0x1020 fs/reiserfs/journal.c:3053

but task is already holding lock:
ffff888028262410 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write_file+0x61/0x200 fs/namespace.c:447

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (sb_writers#9){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1571 [inline]
       sb_start_write+0x4d/0x1c0 include/linux/fs.h:1646
       mnt_want_write_file+0x61/0x200 fs/namespace.c:447
       reiserfs_ioctl+0x178/0x2f0 fs/reiserfs/ioctl.c:103
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:871 [inline]
       __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:857
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #1 (&sbi->lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747
       reiserfs_write_lock_nested+0x5f/0xd0 fs/reiserfs/lock.c:78
       reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:814 [inline]
       lock_journal fs/reiserfs/journal.c:534 [inline]
       do_journal_begin_r+0x35d/0x1020 fs/reiserfs/journal.c:3053
       journal_begin+0x14c/0x360 fs/reiserfs/journal.c:3260
       reiserfs_fill_super+0x1853/0x2620 fs/reiserfs/super.c:2104
       mount_bdev+0x237/0x300 fs/super.c:1629
       legacy_get_tree+0xef/0x190 fs/fs_context.c:662
       vfs_get_tree+0x8c/0x280 fs/super.c:1750
       do_new_mount+0x28f/0xae0 fs/namespace.c:3335
       do_mount fs/namespace.c:3675 [inline]
       __do_sys_mount fs/namespace.c:3884 [inline]
       __se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3861
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (&journal->j_mutex){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain kernel/locking/lockdep.c:3868 [inline]
       __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5136
       lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5753
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747
       reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:813 [inline]
       lock_journal fs/reiserfs/journal.c:534 [inline]
       do_journal_begin_r+0x352/0x1020 fs/reiserfs/journal.c:3053
       journal_begin+0x14c/0x360 fs/reiserfs/journal.c:3260
       reiserfs_dirty_inode+0x120/0x240 fs/reiserfs/super.c:710
       __mark_inode_dirty+0x305/0xd90 fs/fs-writeback.c:2435
       mark_inode_dirty include/linux/fs.h:2237 [inline]
       reiserfs_ioctl+0x24e/0x2f0 fs/reiserfs/ioctl.c:111
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:871 [inline]
       __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:857
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x41/0xc0 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_mutex --> &sbi->lock --> sb_writers#9

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(sb_writers#9);
                               lock(&sbi->lock);
                               lock(sb_writers#9);
  lock(&journal->j_mutex);

 *** DEADLOCK ***

1 lock held by syz-executor363/5030:
 #0: ffff888028262410 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write_file+0x61/0x200 fs/namespace.c:447

stack backtrace:
CPU: 1 PID: 5030 Comm: syz-executor363 Not tainted 6.6.0-rc7-syzkaller-00151-g56567a20b22b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 check_noncircular+0x375/0x4a0 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain kernel/locking/lockdep.c:3868 [inline]
 __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5136
 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5753
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747
 reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:813 [inline]
 lock_journal fs/reiserfs/journal.c:534 [inline]
 do_journal_begin_r+0x352/0x1020 fs/reiserfs/journal.c:3053
 journal_begin+0x14c/0x360 fs/reiserfs/journal.c:3260
 reiserfs_dirty_inode+0x120/0x240 fs/reiserfs/super.c:710
 __mark_inode_dirty+0x305/0xd90 fs/fs-writeback.c:2435
 mark_inode_dirty include/linux/fs.h:2237 [inline]
 reiserfs_ioctl+0x24e/0x2f0 fs/reiserfs/ioctl.c:111
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:871 [inline]
 __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:857
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc69a37d5c9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 00 00 90 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:00007fff7102e1f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fff7102e3c8 RCX: 00007fc69a37d5c9
RDX: 0000000020000000 RSI: 0000000040087602 RDI: 0000000000000003

Crashes (227):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/10/28 12:46 upstream 56567a20b22b 3c418d72 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2023/10/28 03:30 upstream 750b95887e56 3c418d72 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2023/10/28 02:40 upstream 750b95887e56 3c418d72 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2023/05/25 09:40 upstream 933174ae28ba 4bce1a3e .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/20 16:51 upstream b6e7fdfd6f6a 5bb70014 .config strace log report syz C [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in do_journal_begin_r
2022/11/20 16:07 upstream 77c51ba552a1 5bb70014 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/20 15:52 upstream 77c51ba552a1 5bb70014 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/20 13:36 upstream b6e7fdfd6f6a 5bb70014 .config strace log report syz C [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in do_journal_begin_r
2022/11/20 07:44 upstream fe24a97cf254 5bb70014 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/19 16:45 upstream ab290eaddc4c 5bb70014 .config strace log report syz C [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/19 13:58 upstream ab290eaddc4c 5bb70014 .config strace log report syz C [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/19 12:58 upstream ab290eaddc4c 5bb70014 .config strace log report syz C [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/18 09:44 upstream 84368d882b96 5bb70014 .config strace log report syz C [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/17 21:34 upstream 81ac25651a62 4ba8ab94 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/17 06:24 upstream 59d0d52c30d4 3a127a31 .config strace log report syz C [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/17 02:50 upstream 59d0d52c30d4 3a127a31 .config strace log report syz C [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/16 15:59 upstream 81e7cfa3a9eb 3a127a31 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/16 03:04 upstream 81e7cfa3a9eb 3a127a31 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/16 00:23 upstream 81e7cfa3a9eb 3a127a31 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/15 20:51 upstream e01d50cbd6ee 97de9cfc .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in do_journal_begin_r
2022/11/14 10:56 upstream 094226ad94f4 943f4cb8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/14 09:47 upstream 094226ad94f4 7ba4d859 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/14 06:51 upstream af7a05689189 7ba4d859 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/14 06:35 upstream af7a05689189 3ead01ad .config strace log report syz C [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in do_journal_begin_r
2022/11/14 05:40 upstream af7a05689189 3ead01ad .config strace log report syz C [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in do_journal_begin_r
2022/11/14 01:26 upstream af7a05689189 3ead01ad .config strace log report syz C [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in do_journal_begin_r
2022/11/13 21:46 upstream af7a05689189 7ba4d859 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/13 17:44 upstream af7a05689189 7ba4d859 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/13 16:27 upstream fef7fd48922d 3ead01ad .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root possible deadlock in do_journal_begin_r
2022/11/12 23:39 upstream 8f2975c2bb4c f42ee5d8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/12 10:06 upstream 8f2975c2bb4c f42ee5d8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/11 19:59 upstream eb037f16f7e8 f42ee5d8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/11 18:07 upstream 4bbf3422df78 f42ee5d8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/11 12:28 upstream 4bbf3422df78 f42ee5d8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/11 11:59 upstream 4bbf3422df78 f42ee5d8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/11 07:41 upstream 4bbf3422df78 f42ee5d8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/10 10:19 upstream f67dd6ce0723 b2488a87 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/10 08:05 upstream f67dd6ce0723 b2488a87 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/08 13:21 upstream 59f2f4b8a757 060f945e .config strace log report syz C [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/06 22:58 upstream 089d1c31224e 6d752409 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/06 06:32 upstream b208b9fbbcba 6d752409 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/05 08:05 upstream 64c3dd0b98f5 6d752409 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/10/05 11:05 upstream 0326074ff465 267e3bb1 .config strace log report syz C [disk image] [vmlinux] [mounted in repro] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/07 08:27 linux-next 0cdb3579f1ee 6d752409 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root possible deadlock in do_journal_begin_r
2022/11/07 01:22 linux-next 0cdb3579f1ee 6d752409 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root possible deadlock in do_journal_begin_r
2022/11/06 17:20 linux-next 0cdb3579f1ee 6d752409 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root possible deadlock in do_journal_begin_r
2023/11/12 07:04 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8de1e7afcc1c 6d6dbf8a .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 possible deadlock in do_journal_begin_r
2023/11/11 18:35 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8de1e7afcc1c 6d6dbf8a .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 possible deadlock in do_journal_begin_r
2023/10/29 06:42 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8de1e7afcc1c 3c418d72 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 possible deadlock in do_journal_begin_r
2023/10/15 02:02 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 249eb8f39efb 6388bc36 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 possible deadlock in do_journal_begin_r
2022/09/27 17:23 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci c194837ebb57 87840e00 .config console log report syz C [disk image] [vmlinux] ci-upstream-gce-arm64 possible deadlock in do_journal_begin_r
2022/12/21 18:29 upstream b6bb9676f216 4067838e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in do_journal_begin_r
2022/12/18 20:26 upstream f9ff5644bcc0 05494336 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in do_journal_begin_r
2022/12/12 16:41 upstream 830b3c68c1fb 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/12/12 11:14 upstream 4cee37b3a4e6 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/12/12 00:18 upstream 4cee37b3a4e6 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/12/11 20:12 upstream 296a7b7eb792 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/12/09 22:32 upstream 0d1409e4ff08 67be1ae7 .config console log report info ci-qemu-upstream possible deadlock in do_journal_begin_r
2022/12/09 21:26 upstream 0d1409e4ff08 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/21 11:26 upstream eb7081409f94 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/21 06:28 upstream eb7081409f94 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/20 22:45 upstream 77c51ba552a1 5bb70014 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/20 13:17 upstream fe24a97cf254 5bb70014 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/20 03:38 upstream fe24a97cf254 5bb70014 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/19 23:44 upstream fe24a97cf254 5bb70014 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/19 17:52 upstream ab290eaddc4c 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/19 09:51 upstream ab290eaddc4c 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/19 08:30 upstream ab290eaddc4c 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/19 07:20 upstream ab290eaddc4c 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/19 01:01 upstream ab290eaddc4c 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/18 21:17 upstream ab290eaddc4c 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/18 18:18 upstream 84368d882b96 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/18 16:39 upstream 84368d882b96 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/18 12:03 upstream 84368d882b96 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/18 07:59 upstream 84368d882b96 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/18 04:22 upstream 84368d882b96 5bb70014 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/18 01:24 upstream 81ac25651a62 4ba8ab94 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/18 00:15 upstream 81ac25651a62 4ba8ab94 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/17 14:42 upstream cc675d22e422 3a127a31 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/17 12:17 upstream cc675d22e422 3a127a31 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/17 08:38 upstream cc675d22e422 3a127a31 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/17 04:09 upstream 59d0d52c30d4 3a127a31 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/16 21:38 upstream 59d0d52c30d4 3a127a31 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/16 20:28 upstream 59d0d52c30d4 3a127a31 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/16 17:45 upstream 59d0d52c30d4 3a127a31 .config console log report info ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/16 12:40 upstream 81e7cfa3a9eb 3a127a31 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/16 10:56 upstream 81e7cfa3a9eb 3a127a31 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/16 09:30 upstream 81e7cfa3a9eb 3a127a31 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/15 22:57 upstream 81e7cfa3a9eb 3a127a31 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2022/11/15 20:39 upstream e01d50cbd6ee 97de9cfc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in do_journal_begin_r
2024/01/20 15:34 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 0802e17d9aca 9bd8dcda .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in do_journal_begin_r
2023/10/15 01:49 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 249eb8f39efb 6388bc36 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in do_journal_begin_r
2022/12/22 15:01 linux-next e45fb347b630 c692fab1 .config console log report info ci-upstream-linux-next-kasan-gce-root possible deadlock in do_journal_begin_r
2022/12/22 11:58 linux-next e45fb347b630 c692fab1 .config console log report info ci-upstream-linux-next-kasan-gce-root possible deadlock in do_journal_begin_r
2022/12/18 23:31 linux-next ca39c4daa6f7 05494336 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in do_journal_begin_r
2022/12/13 14:34 linux-next 39ab32797f07 67be1ae7 .config console log report info ci-upstream-linux-next-kasan-gce-root possible deadlock in do_journal_begin_r
* Struck through repros no longer work on HEAD.