syzbot


WARNING in __ext4_journal_start_sb

Status: upstream: reported C repro on 2024/04/27 20:56
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+85d8bf8b2759214b194b@syzkaller.appspotmail.com
First crash: 211d, last: 56d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [ext4?] WARNING in __ext4_journal_start_sb 0 (1) 2024/04/27 20:56
Last patch testing requests (3)
Created Duration User Patch Repo Result
2024/09/26 04:20 30m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2024/07/17 17:31 33m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2024/05/07 21:13 25m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 9973 at fs/ext4/ext4_jbd2.c:73 __ext4_journal_start_sb+0x444/0x92c fs/ext4/ext4_jbd2.c:105
Modules linked in:
CPU: 0 PID: 9973 Comm: syz-executor391 Not tainted 6.9.0-rc4-syzkaller-g6a71d2909427 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
pstate: 80401005 (Nzcv daif +PAN -UAO -TCO -DIT +SSBS BTYPE=--)
pc : __ext4_journal_start_sb+0x444/0x92c fs/ext4/ext4_jbd2.c:105
lr : ext4_journal_check_start fs/ext4/ext4_jbd2.c:73 [inline]
lr : __ext4_journal_start_sb+0x440/0x92c fs/ext4/ext4_jbd2.c:105
sp : ffff80009c0474b0
x29: ffff80009c0474c0 x28: 1fffe00018de8cc7 x27: dfff800000000000
x26: 0000000070818001 x25: ffff0000c6f46638 x24: ffff0000c6f46000
x23: 0000000000000001 x22: 0000000000000000 x21: 0000000000000000
x20: ffffffffffffffe2 x19: ffff0000d9ac6280 x18: 1fffe000367b9596
x17: ffff80008ee7d000 x16: ffff800080332544 x15: 0000000000000001
x14: 1fffe0001b750b2b x13: 0000000000000000 x12: 0000000000000000
x11: ffff60001b750b2c x10: 0000000000ff0100 x9 : 0000000000000000
x8 : ffff0000dbfe8000 x7 : ffff800080c13aac x6 : 0000000000000008
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
 __ext4_journal_start_sb+0x444/0x92c fs/ext4/ext4_jbd2.c:105
 ext4_sample_last_mounted fs/ext4/file.c:837 [inline]
 ext4_file_open+0x3c8/0x590 fs/ext4/file.c:866
 do_dentry_open+0x778/0x12b4 fs/open.c:955
 vfs_open+0x7c/0x90 fs/open.c:1089
 do_open fs/namei.c:3642 [inline]
 path_openat+0x1f6c/0x2830 fs/namei.c:3799
 do_filp_open+0x1bc/0x3cc fs/namei.c:3826
 do_sys_openat2+0x124/0x1b8 fs/open.c:1406
 do_sys_open fs/open.c:1421 [inline]
 __do_sys_openat fs/open.c:1437 [inline]
 __se_sys_openat fs/open.c:1432 [inline]
 __arm64_sys_openat+0x1f0/0x240 fs/open.c:1432
 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48
 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:133
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:152
 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712
 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730
 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598
irq event stamp: 186
hardirqs last  enabled at (185): [<ffff800080c164c4>] seqcount_lockdep_reader_access+0x80/0x100 include/linux/seqlock.h:74
hardirqs last disabled at (186): [<ffff80008ae6da08>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:470
softirqs last  enabled at (8): [<ffff800080031848>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (6): [<ffff800080031814>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/23 20:50 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 6a71d2909427 21339d7b .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 WARNING in __ext4_journal_start_sb
* Struck through repros no longer work on HEAD.