general protection fault in lbmStartIO

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a1b977b4 Linux 4.19.150
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=170a64cf900000
kernel config: https://syzkaller.appspot.com/x/.config?x=c14008c8da1ca4d4
dashboard link: https://syzkaller.appspot.com/bug?extid=d4368afa9c78c1e043a7
compiler: gcc (GCC) 10.1.0-syz 20200507

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

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

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
CPU: 0 PID: 10466 Comm: syz-executor.3 Not tainted 4.19.150-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:lbmStartIO+0x14b/0x4a0 fs/jfs/jfs_logmgr.c:2142
Code: c1 ea 03 80 3c 02 00 0f 85 13 03 00 00 48 b8 00 00 00 00 00 fc ff df 4d 8b 6c 24 20 49 8d bd e0 00 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 21 03 00 00 4d 8b ad e0 00 00 00 4d 39 ee 74 67
RSP: 0018:ffff888049d07910 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: ffff88809e855900 RCX: 0000000000000003
RDX: 000000000000001c RSI: ffffffff82911932 RDI: 00000000000000e0
RBP: ffff88804aa46c80 R08: 0000000000000001 R09: 000000000000003f
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888087ad9b40
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000002
FS: 00007f0c7ec26700(0000) GS:ffff8880ae200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000016a9e60 CR3: 0000000083d12000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lbmWrite+0x299/0x3c0 fs/jfs/jfs_logmgr.c:2091
lmNextPage.isra.0+0x285/0x740 fs/jfs/jfs_logmgr.c:637
lmWriteRecord+0x917/0xea0 fs/jfs/jfs_logmgr.c:550
lmLog+0x294/0xb60 fs/jfs/jfs_logmgr.c:327
logMOUNT fs/jfs/jfs_mount.c:504 [inline]
jfs_mount_rw+0x3e5/0x4aa fs/jfs/jfs_mount.c:286
jfs_fill_super+0x814/0xb50 fs/jfs/super.c:598
mount_bdev+0x2fc/0x3b0 fs/super.c:1158
mount_fs+0xa3/0x318 fs/super.c:1261
vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
vfs_kern_mount fs/namespace.c:951 [inline]
do_new_mount fs/namespace.c:2469 [inline]
do_mount+0x51c/0x2f10 fs/namespace.c:2799
ksys_mount+0xcf/0x130 fs/namespace.c:3015
__do_sys_mount fs/namespace.c:3029 [inline]
__se_sys_mount fs/namespace.c:3026 [inline]
__x64_sys_mount+0xba/0x150 fs/namespace.c:3026
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4608aa
Code: b8 a6 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 ad 89 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 8a 89 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007f0c7ec25a88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f0c7ec25b20 RCX: 00000000004608aa
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f0c7ec25ae0
RBP: 00007f0c7ec25ae0 R08: 00007f0c7ec25b20 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 0000000020000200 R15: 00000000200065c0
Modules linked in:
audit: type=1804 audit(1602355734.274:123): pid=10482 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op=invalid_pcr cause=open_writers comm="syz-executor.2" name="/root/syzkaller-testdir070762241/syzkaller.9dhb4a/43/file1/file0" dev="loop2" ino=105 res=1
audit: type=1804 audit(1602355734.604:124): pid=10492 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op=invalid_pcr cause=open_writers comm="syz-executor.1" name="/root/syzkaller-testdir330771896/syzkaller.W9GiSY/38/file1/file0" dev="loop1" ino=107 res=1
---[ end trace 3991b0a216b0c802 ]---
RIP: 0010:lbmStartIO+0x14b/0x4a0 fs/jfs/jfs_logmgr.c:2142
Code: c1 ea 03 80 3c 02 00 0f 85 13 03 00 00 48 b8 00 00 00 00 00 fc ff df 4d 8b 6c 24 20 49 8d bd e0 00 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 21 03 00 00 4d 8b ad e0 00 00 00 4d 39 ee 74 67
audit: type=1804 audit(1602355734.734:125): pid=10498 uid=0 auid=0 ses=4 subj=system_u:system_r:kernel_t:s0 op=invalid_pcr cause=open_writers comm="syz-executor.5" name="/root/syzkaller-testdir952589513/syzkaller.2UFRwL/43/file0" dev="sda1" ino=16043 res=1
RSP: 0018:ffff888049d07910 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: ffff88809e855900 RCX: 0000000000000003
RDX: 000000000000001c RSI: ffffffff82911932 RDI: 00000000000000e0
RBP: ffff88804aa46c80 R08: 0000000000000001 R09: 000000000000003f
R10: 0000000000000005 R11: 0000000000000000 R12: ffff888087ad9b40
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000002
FS: 00007f0c7ec26700(0000) GS:ffff8880ae200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff590a5f9c CR3: 0000000083d12000 CR4: 00000000001406f0
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.

[syzbot]

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