[jfs?] WARNING in jfs_flush_journal

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15e8d8ff880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=f4c9e255a5df6d2bae73
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

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

nla_parse: 57 callbacks suppressed
netlink: 40 bytes leftover after parsing attributes in process `syz-executor.4'.
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4408 at fs/jfs/jfs_logmgr.c:1634 jfs_flush_journal.part.0.cold+0x11/0x3e fs/jfs/jfs_logmgr.c:1634
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 4408 Comm: syz-executor.1 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:jfs_flush_journal.part.0.cold+0x11/0x3e fs/jfs/jfs_logmgr.c:1634
Code: 11 9b 88 e8 6d cd fa ff 0f 0b e8 fb 9b 69 f9 e8 46 5f 9f f9 e8 70 ff ff ff e8 ec 9b 69 f9 48 c7 c7 40 12 9b 88 e8 4b cd fa ff <0f> 0b e9 99 4b 7f fa e8 d4 9b 69 f9 48 c7 c1 00 12 9b 88 ba 4a 06
RSP: 0018:ffff88809f537bc8 EFLAGS: 00010282
RAX: 0000000000000024 RBX: ffff88809bcb4b40 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1013ea6f6b
RBP: ffff88809bcb4940 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff88809bcb4ac8
R13: ffffed1013796959 R14: dffffc0000000000 R15: 1ffff11013796968
jfs_flush_journal+0x23/0x30 fs/jfs/jfs_logmgr.c:1537
jfs_umount+0xbf/0x310 fs/jfs/jfs_umount.c:71
jfs_put_super+0x61/0x140 fs/jfs/super.c:223
generic_shutdown_super+0x144/0x370 fs/super.c:456
kill_block_super+0x97/0xf0 fs/super.c:1185
deactivate_locked_super+0x94/0x160 fs/super.c:329
deactivate_super+0x174/0x1a0 fs/super.c:360
cleanup_mnt+0x1a8/0x290 fs/namespace.c:1098
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f9a30749517
Code: ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 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:00007fff8dc8f768 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f9a30749517
RDX: 00007fff8dc8f83a RSI: 000000000000000a RDI: 00007fff8dc8f830
RBP: 00007fff8dc8f830 R08: 00000000ffffffff R09: 00007fff8dc8f600
R10: 00005555558bf903 R11: 0000000000000246 R12: 00007f9a307a2b24
R13: 00007fff8dc908f0 R14: 00005555558bf810 R15: 00007fff8dc90930
Kernel Offset: disabled
Rebooting in 86400 seconds..


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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y

console output: https://syzkaller.appspot.com/x/log.txt?x=1406a038480000

kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=f4c9e255a5df6d2bae73
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12b871a8480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1416dd74480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/0bd626d79421/mount_0.gz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 8087 at fs/jfs/jfs_logmgr.c:1634 jfs_flush_journal.part.0.cold+0x11/0x3e fs/jfs/jfs_logmgr.c:1634

Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 8087 Comm: syz-executor221 Not tainted 4.19.211-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:jfs_flush_journal.part.0.cold+0x11/0x3e fs/jfs/jfs_logmgr.c:1634
Code: 11 9b 88 e8 6d cd fa ff 0f 0b e8 fb 9b 69 f9 e8 46 5f 9f f9 e8 70 ff ff ff e8 ec 9b 69 f9 48 c7 c7 40 12 9b 88 e8 4b cd fa ff <0f> 0b e9 99 4b 7f fa e8 d4 9b 69 f9 48 c7 c1 00 12 9b 88 ba 4a 06

RSP: 0018:ffff888091dffbc8 EFLAGS: 00010282
RAX: 0000000000000024 RBX: ffff88809e413400 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed10123bff6b
RBP: ffff88809e413200 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff88809e413388
R13: ffffed1013c82671 R14: dffffc0000000000 R15: 1ffff11013c82680

jfs_flush_journal+0x23/0x30 fs/jfs/jfs_logmgr.c:1537
jfs_umount+0xbf/0x310 fs/jfs/jfs_umount.c:71
jfs_put_super+0x61/0x140 fs/jfs/super.c:223
generic_shutdown_super+0x144/0x370 fs/super.c:456
kill_block_super+0x97/0xf0 fs/super.c:1185
deactivate_locked_super+0x94/0x160 fs/super.c:329
deactivate_super+0x174/0x1a0 fs/super.c:360
cleanup_mnt+0x1a8/0x290 fs/namespace.c:1098
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe

RIP: 0033:0x7f3387c288e7
Code: 07 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe9846d108 EFLAGS: 00000202 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f3387c288e7
RDX: 00007ffe9846d1c9 RSI: 000000000000000a RDI: 00007ffe9846d1c0
RBP: 00007ffe9846d1c0 R08: 00000000ffffffff R09: 00007ffe9846cfa0
R10: 000055555714c683 R11: 0000000000000202 R12: 00007ffe9846e220
R13: 000055555714c5f0 R14: 00007ffe9846d130 R15: 0000000000000001