syzbot


possible deadlock in do_journal_begin_r

Status: upstream: reported C repro on 2023/06/19 07:49
Bug presence: origin:upstream
Labels: missing-backport
[Documentation on labels]
Reported-by: syzbot+f6ec13710cba2de48467@syzkaller.appspotmail.com
First crash: 756d, last: 7d02h
Fix commit to backport (bisect log) :
tree: upstream
commit fb6f20ecb121cef4d7946f834a6ee867c4e21b4a
Author: Jan Kara <jack@suse.cz>
Date: Thu Oct 17 10:28:23 2024 +0000

  reiserfs: The last commit

  
Fix bisection: failed (error log, bisect log)
  
Bug presence (3)
Date Name Commit Repro Result
2024/12/13 linux-5.15.y (ToT) 0a51d2d4527b C [report] possible deadlock in page_cache_ra_unbounded
2023/06/19 upstream (ToT) 45a3e24f65e9 C [report] possible deadlock in page_cache_ra_unbounded
2024/12/13 upstream (ToT) f932fb9b4074 C Didn't crash
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 possible deadlock in do_journal_begin_r reiserfs 4 C error 45 936d 1021d 0/1 upstream: reported C repro on 2022/09/27 10:45
linux-4.14 possible deadlock in do_journal_begin_r reiserfs 4 C 55 863d 1013d 0/1 upstream: reported C repro on 2022/10/05 14:07
upstream possible deadlock in do_journal_begin_r reiserfs 4 C error error 227 541d 1017d 0/29 auto-obsoleted due to no activity on 2024/05/26 14:27
linux-6.1 possible deadlock in do_journal_begin_r origin:upstream missing-backport 4 C done 29 134d 750d 0/3 upstream: reported C repro on 2023/06/25 10:36
Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/07/07 15:13 11m retest repro linux-5.15.y report log
2025/06/22 09:34 19m retest repro linux-5.15.y report log
2025/06/22 09:34 17m retest repro linux-5.15.y report log
2025/05/31 11:29 10m retest repro linux-5.15.y report log
2025/05/31 11:29 10m retest repro linux-5.15.y report log
2025/05/31 11:29 10m retest repro linux-5.15.y report log
2025/05/31 11:29 10m retest repro linux-5.15.y report log
2025/05/16 05:52 13m retest repro linux-5.15.y report log
2025/05/16 05:52 9m retest repro linux-5.15.y report log
2025/05/16 05:52 14m retest repro linux-5.15.y report log
Fix bisection attempts (8)
Created Duration User Patch Repo Result
2025/05/01 02:09 10h25m fix candidate upstream OK (1) job log
2024/07/07 07:06 0m bisect fix linux-5.15.y error job log
2024/06/06 01:25 2h23m bisect fix linux-5.15.y OK (0) job log log
2024/03/01 19:20 1h05m bisect fix linux-5.15.y OK (0) job log log
2024/01/22 10:49 1h10m bisect fix linux-5.15.y OK (0) job log log
2023/12/23 07:54 57m bisect fix linux-5.15.y OK (0) job log log
2023/10/05 19:41 58m bisect fix linux-5.15.y OK (0) job log log
2023/08/08 07:23 2h41m bisect fix linux-5.15.y OK (0) job log log

Sample crash report:
REISERFS (device loop0): journal params: device loop0, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30
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
5.15.185-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor428/4166 is trying to acquire lock:
ffffc90002e910f0 (&journal->j_mutex){+.+.}-{3:3}, at: reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:814 [inline]
ffffc90002e910f0 (&journal->j_mutex){+.+.}-{3:3}, at: lock_journal fs/reiserfs/journal.c:534 [inline]
ffffc90002e910f0 (&journal->j_mutex){+.+.}-{3:3}, at: do_journal_begin_r+0x37a/0x1010 fs/reiserfs/journal.c:3045

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

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:1811 [inline]
       sb_start_write+0x4f/0x1c0 include/linux/fs.h:1881
       mnt_want_write_file+0x5c/0x200 fs/namespace.c:421
       reiserfs_ioctl+0x10a/0x330 fs/reiserfs/ioctl.c:103
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #1 (&sbi->lock){+.+.}-{3:3}:
       __mutex_lock_common+0x1eb/0x2390 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       reiserfs_write_lock_nested+0x5c/0xd0 fs/reiserfs/lock.c:78
       reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:815 [inline]
       lock_journal fs/reiserfs/journal.c:534 [inline]
       do_journal_begin_r+0x385/0x1010 fs/reiserfs/journal.c:3045
       journal_begin+0x148/0x350 fs/reiserfs/journal.c:3253
       reiserfs_fill_super+0x1654/0x23e0 fs/reiserfs/super.c:2108
       mount_bdev+0x287/0x3c0 fs/super.c:1400
       legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
       vfs_get_tree+0x88/0x270 fs/super.c:1530
       do_new_mount+0x24a/0xa40 fs/namespace.c:3010
       do_mount fs/namespace.c:3353 [inline]
       __do_sys_mount fs/namespace.c:3561 [inline]
       __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3538
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (&journal->j_mutex){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
       lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
       __mutex_lock_common+0x1eb/0x2390 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:814 [inline]
       lock_journal fs/reiserfs/journal.c:534 [inline]
       do_journal_begin_r+0x37a/0x1010 fs/reiserfs/journal.c:3045
       journal_begin+0x148/0x350 fs/reiserfs/journal.c:3253
       reiserfs_dirty_inode+0x119/0x240 fs/reiserfs/super.c:710
       __mark_inode_dirty+0x2b0/0xc60 fs/fs-writeback.c:2464
       mark_inode_dirty include/linux/fs.h:2467 [inline]
       reiserfs_ioctl+0x286/0x330 fs/reiserfs/ioctl.c:111
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

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
       ----                    ----
  lock(sb_writers#9);
                               lock(&sbi->lock);
                               lock(sb_writers#9);
  lock(&journal->j_mutex);

 *** DEADLOCK ***

1 lock held by syz-executor428/4166:
 #0: ffff88801abd0460 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write_file+0x5c/0x200 fs/namespace.c:421

stack backtrace:
CPU: 0 PID: 4166 Comm: syz-executor428 Not tainted 5.15.185-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x1eb/0x2390 kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:814 [inline]
 lock_journal fs/reiserfs/journal.c:534 [inline]
 do_journal_begin_r+0x37a/0x1010 fs/reiserfs/journal.c:3045
 journal_begin+0x148/0x350 fs/reiserfs/journal.c:3253
 reiserfs_dirty_inode+0x119/0x240 fs/reiserfs/super.c:710
 __mark_inode_dirty+0x2b0/0xc60 fs/fs-writeback.c:2464
 mark_inode_dirty include/linux/fs.h:2467 [inline]
 reiserfs_ioctl+0x286/0x330 fs/reiserfs/ioctl.c:111
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:874 [inline]
 __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f524e0f9649
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:00007ffd83229dc8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ffd83229f98 RCX: 00007f524e0f9649
RDX: 0000200000000000 RSI: 0000000040087602 RDI: 0000000000000003

Crashes (51):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/23 10:22 linux-5.15.y 1c700860e8bc d6cdfb8a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2024/12/09 07:23 linux-5.15.y 0a51d2d4527b 9ac0fdc6 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2024/03/15 02:19 linux-5.15.y 574362648507 d615901c .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2023/10/15 08:28 linux-5.15.y 02e21884dcf2 f757a323 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2023/06/19 07:49 linux-5.15.y 471e639e59d1 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2025/01/18 22:47 linux-5.15.y 4735586da88e f2cb035c .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2025/01/18 22:27 linux-5.15.y 4735586da88e f2cb035c .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/05/05 19:42 linux-5.15.y 284087d4f7d5 610f2a54 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/04/24 09:07 linux-5.15.y c52b9710c83d 21339d7b .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/04/24 00:44 linux-5.15.y c52b9710c83d 21339d7b .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/04/23 07:04 linux-5.15.y c52b9710c83d 36c961ad .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/03/15 02:44 linux-5.15.y 574362648507 d615901c .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/10/15 22:35 linux-5.15.y 02e21884dcf2 f757a323 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/12/09 06:33 linux-5.15.y 0a51d2d4527b 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2024/03/26 20:23 linux-5.15.y b95c01af2113 454571b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2024/03/26 14:15 linux-5.15.y b95c01af2113 bcd9b39f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2024/03/26 01:16 linux-5.15.y b95c01af2113 bcd9b39f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2024/03/25 12:00 linux-5.15.y b95c01af2113 0ea90952 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2024/03/24 23:08 linux-5.15.y b95c01af2113 0ea90952 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2024/03/23 08:51 linux-5.15.y b95c01af2113 0ea90952 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2024/03/15 00:10 linux-5.15.y 574362648507 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2023/10/15 02:11 linux-5.15.y 02e21884dcf2 f757a323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in do_journal_begin_r
2024/09/09 11:43 linux-5.15.y 14e468424d3e 9750182a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/03/25 12:11 linux-5.15.y b95c01af2113 0ea90952 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/03/23 09:05 linux-5.15.y b95c01af2113 0ea90952 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/03/15 22:27 linux-5.15.y b95c01af2113 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/03/15 20:34 linux-5.15.y b95c01af2113 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/03/15 18:02 linux-5.15.y 574362648507 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/03/15 00:52 linux-5.15.y 574362648507 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2024/03/14 22:44 linux-5.15.y 574362648507 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/11/23 04:23 linux-5.15.y 2a910f4af54d fc59b78e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/11/22 16:46 linux-5.15.y 2a910f4af54d 03e12510 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/11/11 01:20 linux-5.15.y 80529b4968a8 d80eec66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/11/09 02:02 linux-5.15.y 80529b4968a8 4862372a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/11/08 20:13 linux-5.15.y 80529b4968a8 b93f63e8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/11/08 15:05 linux-5.15.y 12952a23a5da b93f63e8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/11/03 02:25 linux-5.15.y 12952a23a5da c4ac074c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/11/02 21:33 linux-5.15.y 12952a23a5da c4ac074c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/11/02 09:08 linux-5.15.y 12952a23a5da 69904c9f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/11/02 06:54 linux-5.15.y 12952a23a5da 69904c9f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/10/31 11:41 linux-5.15.y 12952a23a5da 58499c95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/10/30 17:17 linux-5.15.y 12952a23a5da b5729d82 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/10/27 03:46 linux-5.15.y 12952a23a5da bf285f0c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/10/26 16:37 linux-5.15.y 12952a23a5da 23afc60f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/10/25 15:52 linux-5.15.y 12952a23a5da 17e6d526 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/10/25 13:09 linux-5.15.y 12952a23a5da 17e6d526 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/10/23 17:27 linux-5.15.y 00c03985402e 989a3687 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/10/23 14:34 linux-5.15.y 00c03985402e 989a3687 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/10/20 22:12 linux-5.15.y 00c03985402e 361b23dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/10/20 03:53 linux-5.15.y 00c03985402e a42250d2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
2023/10/15 02:19 linux-5.15.y 02e21884dcf2 f757a323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in do_journal_begin_r
* Struck through repros no longer work on HEAD.