[v6.1] kernel BUG in jfs_flush_journal

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cd5d98c0556c Linux 6.1.86
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1521c42d180000
kernel config: https://syzkaller.appspot.com/x/.config?x=cc6a54650e83f88f
dashboard link: https://syzkaller.appspot.com/bug?extid=85a8c95eb878392e9b04
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/35b2c3edb8aa/disk-cd5d98c0.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2a5efc7ec06c/vmlinux-cd5d98c0.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9f02d0ba73da/Image-cd5d98c0.gz.xz

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

BUG at fs/jfs/jfs_logmgr.c:1588 assert(list_empty(&log->cqueue))
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_logmgr.c:1588!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 5921 Comm: syz-executor.1 Not tainted 6.1.86-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : jfs_flush_journal+0xd1c/0xd64 fs/jfs/jfs_logmgr.c:1588
lr : jfs_flush_journal+0xd1c/0xd64 fs/jfs/jfs_logmgr.c:1588
sp : ffff80001e3376e0
x29: ffff80001e3377d0 x28: dfff800000000000 x27: 1fffe0001e7eee45
x26: 1fffe0001e7eee35 x25: 1fffe0001e7eee00 x24: ffff0000e2574e60
x23: ffff0000f3f77000 x22: ffff0000f3f77228 x21: 00000000000000c8
x20: ffff0000f3f771a8 x19: ffff0000f3f77000 x18: ffff80001e336b98
x17: 0000000000000000 x16: ffff800012156b1c x15: 0000000000000000
x14: 00000000ffffffff x13: 0000000000000001 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : b7e43f56beb0d700
x8 : b7e43f56beb0d700 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001e336ff8 x4 : ffff800015922b00 x3 : ffff80000aa9130c
x2 : ffff0001b4359cd0 x1 : 0000000100000000 x0 : 0000000000000040
Call trace:
jfs_flush_journal+0xd1c/0xd64 fs/jfs/jfs_logmgr.c:1588
jfs_umount+0xf8/0x338 fs/jfs/jfs_umount.c:58
jfs_put_super+0x90/0x188 fs/jfs/super.c:194
generic_shutdown_super+0x130/0x328 fs/super.c:501
kill_block_super+0x70/0xdc fs/super.c:1459
deactivate_locked_super+0xac/0x124 fs/super.c:332
deactivate_super+0xf0/0x110 fs/super.c:363
cleanup_mnt+0x394/0x41c fs/namespace.c:1186
__cleanup_mnt+0x20/0x30 fs/namespace.c:1193
task_work_run+0x240/0x2f0 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
do_notify_resume+0x2148/0x3474 arch/arm64/kernel/signal.c:1132
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_svc+0x9c/0x168 arch/arm64/kernel/entry-common.c:638
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: f0046243 91240063 5280c682 95956614 (d4210000)
---[ end trace 0000000000000000 ]---


---
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