[v5.15] kernel BUG in jbd2_journal_get_create_access

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 38d4ca22a528 Linux 5.15.124
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1137bbb9a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=45eb463798d34fdb
dashboard link: https://syzkaller.appspot.com/bug?extid=a020f22f2a15493ac30b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0470c022da0e/disk-38d4ca22.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/56cf48a83529/vmlinux-38d4ca22.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ac8ac64c33ec/bzImage-38d4ca22.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a020f2...@syzkaller.appspotmail.com

------------[ cut here ]------------
kernel BUG at fs/jbd2/transaction.c:1292!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 7195 Comm: syz-executor.2 Not tainted 5.15.124-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
RIP: 0010:jbd2_journal_get_create_access+0x44b/0x450 fs/jbd2/transaction.c:1289
Code: ff ff ff 48 89 ef e8 d4 e7 99 ff e9 24 ff ff ff e8 9a 6e 50 ff 0f 0b e8 93 6e 50 ff 0f 0b e8 8c 6e 50 ff 0f 0b e8 85 6e 50 ff <0f> 0b 0f 1f 00 55 41 57 41 56 41 55 41 54 53 48 83 ec 30 41 89 d7
RSP: 0018:ffffc9000323f830 EFLAGS: 00010293
RAX: ffffffff822f937b RBX: ffff888047bb3800 RCX: ffff888077380000
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000002
RBP: 0000000000000003 R08: ffffffff822f90c6 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff8880257d4f20 R14: ffff888025994000 R15: ffff8880254095a0
FS: 0000555557470480(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3f77297000 CR3: 000000001f0f6000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__ext4_journal_get_create_access+0xaf/0x550 fs/ext4/ext4_jbd2.c:323
ext4_getblk+0x403/0x710 fs/ext4/inode.c:870
ext4_bread+0x2a/0x170 fs/ext4/inode.c:899
ext4_append+0x31f/0x5c0 fs/ext4/namei.c:83
ext4_init_new_dir+0x33a/0xa20 fs/ext4/namei.c:2976
ext4_mkdir+0x4f2/0xce0 fs/ext4/namei.c:3022
vfs_mkdir+0x419/0x640 fs/namei.c:3994
do_mkdirat+0x260/0x520 fs/namei.c:4019
__do_sys_mkdirat fs/namei.c:4034 [inline]
__se_sys_mkdirat fs/namei.c:4032 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4032
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7ff6c5d885e7
Code: 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 02 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff71cea0f8 EFLAGS: 00000202 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fff71cea180 RCX: 00007ff6c5d885e7
RDX: 00000000000001ff RSI: 00007fff71cea180 RDI: 00000000ffffff9c
RBP: 00007fff71cea15c R08: 0000000000000006 R09: 00007fff71ce9e94
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000032
R13: 00000000002c2635 R14: 00000000002c24cb R15: 0000000000000017
</TASK>
Modules linked in:
---[ end trace 6ebc8c2ed7ea4dda ]---
RIP: 0010:jbd2_journal_get_create_access+0x44b/0x450 fs/jbd2/transaction.c:1289
Code: ff ff ff 48 89 ef e8 d4 e7 99 ff e9 24 ff ff ff e8 9a 6e 50 ff 0f 0b e8 93 6e 50 ff 0f 0b e8 8c 6e 50 ff 0f 0b e8 85 6e 50 ff <0f> 0b 0f 1f 00 55 41 57 41 56 41 55 41 54 53 48 83 ec 30 41 89 d7
RSP: 0018:ffffc9000323f830 EFLAGS: 00010293
RAX: ffffffff822f937b RBX: ffff888047bb3800 RCX: ffff888077380000
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000002
RBP: 0000000000000003 R08: ffffffff822f90c6 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff8880257d4f20 R14: ffff888025994000 R15: ffff8880254095a0
FS: 0000555557470480(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3f77297000 CR3: 000000001f0f6000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.