[v5.15] WARNING in __ext4_journal_start_sb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c16c81c81336 Linux 5.15.178
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12bac718580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3ca28fba9b2e5c5
dashboard link: https://syzkaller.appspot.com/bug?extid=841d823b968a38b23967
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3f2947e5e4dc/disk-c16c81c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7034800fdaa8/vmlinux-c16c81c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/42337be7c213/Image-c16c81c8.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 335 at fs/ext4/ext4_jbd2.c:75 ext4_journal_check_start fs/ext4/ext4_jbd2.c:75 [inline]
WARNING: CPU: 0 PID: 335 at fs/ext4/ext4_jbd2.c:75 __ext4_journal_start_sb+0x44c/0x70c fs/ext4/ext4_jbd2.c:98
Modules linked in:
CPU: 0 PID: 335 Comm: kworker/u4:4 Not tainted 5.15.178-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Workqueue: writeback wb_workfn (flush-7:8)
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ext4_journal_check_start fs/ext4/ext4_jbd2.c:75 [inline]
pc : __ext4_journal_start_sb+0x44c/0x70c fs/ext4/ext4_jbd2.c:98
lr : ext4_journal_check_start fs/ext4/ext4_jbd2.c:75 [inline]
lr : __ext4_journal_start_sb+0x44c/0x70c fs/ext4/ext4_jbd2.c:98
sp : ffff80001ff36d10
x29: ffff80001ff36d20 x28: 1fffe0001af2a0cf x27: dfff800000000000
x26: 0000000000000004 x25: ffff0000d7950678 x24: ffff0000d7950000
x23: 0000000000000006 x22: 0000000000000000 x21: 0000000000000002
x20: 0000000000000afc x19: 0000000000000080 x18: 0000000000000000
x17: 0000000000000000 x16: ffff8000082eae30 x15: 0000000000000406
x14: 00000000ffff8000 x13: 00000000d0dd6a71 x12: 0000000000000001
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000c7d11b40
x8 : ffff800008d28564 x7 : 0000000000000000 x6 : 000000000000003f
x5 : 0000000000000080 x4 : 0000000000000000 x3 : 0000000000000006
x2 : 0000000000000000 x1 : 0000000000000004 x0 : 0000000000000004
Call trace:
ext4_journal_check_start fs/ext4/ext4_jbd2.c:75 [inline]
__ext4_journal_start_sb+0x44c/0x70c fs/ext4/ext4_jbd2.c:98
__ext4_journal_start fs/ext4/ext4_jbd2.h:326 [inline]
ext4_writepages+0xd50/0x36fc fs/ext4/inode.c:2811
do_writepages+0x39c/0x5ec mm/page-writeback.c:2386
__writeback_single_inode+0x148/0x13a4 fs/fs-writeback.c:1647
writeback_sb_inodes+0x94c/0x1654 fs/fs-writeback.c:1930
wb_writeback+0x3fc/0xfc8 fs/fs-writeback.c:2104
wb_do_writeback fs/fs-writeback.c:2247 [inline]
wb_workfn+0x3a4/0x1070 fs/fs-writeback.c:2288
process_one_work+0x790/0x11b8 kernel/workqueue.c:2310
worker_thread+0x910/0x1034 kernel/workqueue.c:2457
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
irq event stamp: 3723062
hardirqs last enabled at (3723061): [<ffff8000088d641c>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:231
hardirqs last disabled at (3723062): [<ffff800011b49ab0>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (3722814): [<ffff80000fefe258>] spin_unlock_bh include/linux/spinlock.h:408 [inline]
softirqs last enabled at (3722814): [<ffff80000fefe258>] release_sock+0x1e4/0x270 net/core/sock.c:3279
softirqs last disabled at (3722812): [<ffff80000fefe0b0>] spin_lock_bh include/linux/spinlock.h:368 [inline]
softirqs last disabled at (3722812): [<ffff80000fefe0b0>] release_sock+0x3c/0x270 net/core/sock.c:3266
---[ end trace 67ddf5a86bd2b176 ]---


---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

If the report is a duplicate of another one, 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.