[jfs?] general protection fault in write_special_inodes (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3949d1610004 Linux 4.14.304
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17cb30d9480000
kernel config: https://syzkaller.appspot.com/x/.config?x=db4418ccbf710113
dashboard link: https://syzkaller.appspot.com/bug?extid=929162a820188e95fe76
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/2230a6d7e7f4/disk-3949d161.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9b8d5667f298/vmlinux-3949d161.xz
kernel image: https://storage.googleapis.com/syzbot-assets/825468a3e783/bzImage-3949d161.xz

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

JFS: discard option not supported on device
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 8001 Comm: syz-executor.0 Not tainted 4.14.304-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
task: ffff8880a4cea440 task.stack: ffff888097288000
RIP: 0010:write_special_inodes+0xa6/0x170 fs/jfs/jfs_logmgr.c:221
RSP: 0018:ffff88809728fc08 EFLAGS: 00010206
RAX: 0000000000000006 RBX: ffff88809dc4bdc0 RCX: 000000000000001b
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000030
RBP: dffffc0000000000 R08: ffffffff8b9b07d0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff8168d920
R13: 0000000000000000 R14: ffff88809a6c4dc0 R15: 0000000000000000
FS: 0000555555f78400(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9bdfa00000 CR3: 000000009139e000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
jfs_flush_journal.part.0+0x251/0x600 fs/jfs/jfs_logmgr.c:1595
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:446
kill_block_super+0x95/0xe0 fs/super.c:1161
deactivate_locked_super+0x6c/0xd0 fs/super.c:319
deactivate_super+0x7f/0xa0 fs/super.c:350
cleanup_mnt+0x186/0x2c0 fs/namespace.c:1183
task_work_run+0x11f/0x190 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:191 [inline]
exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164
prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7f5bf2dd4537
RSP: 002b:00007ffca4aee898 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f5bf2dd4537
RDX: 00007ffca4aee96a RSI: 000000000000000a RDI: 00007ffca4aee960
RBP: 00007ffca4aee960 R08: 00000000ffffffff R09: 00007ffca4aee730
R10: 0000555555f79903 R11: 0000000000000246 R12: 00007f5bf2e2db24
R13: 00007ffca4aefa20 R14: 0000555555f79810 R15: 00007ffca4aefa60
Code: 49 8b 7d 30 41 ff d4 48 8d 7b 28 48 89 f8 48 c1 e8 03 80 3c 28 00 0f 85 ab 00 00 00 4c 8b 6b 28 49 8d 7d 30 48 89 f8 48 c1 e8 03 <80> 3c 28 00 0f 85 88 00 00 00 49 8b 7d 30 41 ff d4 48 8d bb b0
RIP: write_special_inodes+0xa6/0x170 fs/jfs/jfs_logmgr.c:221 RSP: ffff88809728fc08
audit: type=1800 audit(1675360445.183:15): pid=10189 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="file0" dev="sda1" ino=13977 res=0
F2FS-fs (loop1): Mismatch start address, segment0(512) cp_blkaddr(605)
audit: type=1804 audit(1675360445.263:16): pid=10191 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir2134120142/syzkaller.mL3nAK/27/file0" dev="sda1" ino=13977 res=1
F2FS-fs (loop1): Can't find valid F2FS filesystem in 1th superblock
---[ end trace b43ac15f9d10bf1e ]---
----------------
Code disassembly (best guess):
0: 49 8b 7d 30 mov 0x30(%r13),%rdi
4: 41 ff d4 callq *%r12
7: 48 8d 7b 28 lea 0x28(%rbx),%rdi
b: 48 89 f8 mov %rdi,%rax
e: 48 c1 e8 03 shr $0x3,%rax
12: 80 3c 28 00 cmpb $0x0,(%rax,%rbp,1)
16: 0f 85 ab 00 00 00 jne 0xc7
1c: 4c 8b 6b 28 mov 0x28(%rbx),%r13
20: 49 8d 7d 30 lea 0x30(%r13),%rdi
24: 48 89 f8 mov %rdi,%rax
27: 48 c1 e8 03 shr $0x3,%rax
* 2b: 80 3c 28 00 cmpb $0x0,(%rax,%rbp,1) <-- trapping instruction
2f: 0f 85 88 00 00 00 jne 0xbd
35: 49 8b 7d 30 mov 0x30(%r13),%rdi
39: 41 ff d4 callq *%r12
3c: 48 rex.W
3d: 8d .byte 0x8d
3e: bb .byte 0xbb
3f: b0 .byte 0xb0


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