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=11064b8c480000
kernel config:
https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link:
https://syzkaller.appspot.com/bug?extid=588401b5ca79569e60ad
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+588401...@syzkaller.appspotmail.com
BUG at fs/jfs/jfs_txnmgr.c:939 assert(mp->nohomeok > 0)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:939!
audit: type=1804 audit(1671907054.018:552): pid=4119 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.1" name="/root/syzkaller-testdir2799805300/syzkaller.0hjXVx/2534/bus" dev="sda1" ino=14802 res=1
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 1985 Comm: jfsCommit Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:txUnlock.cold+0x4a/0x72 fs/jfs/jfs_txnmgr.c:939
audit: type=1804 audit(1671907054.048:553): pid=4119 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=ToMToU comm="syz-executor.1" name="/root/syzkaller-testdir2799805300/syzkaller.0hjXVx/2534/bus" dev="sda1" ino=14802 res=1
Code: eb cc fa ff 0f 0b e8 79 9b 69 f9 48 c7 c1 a0 16 9b 88 ba ab 03 00 00 48 c7 c6 20 16 9b 88 48 c7 c7 60 16 9b 88 e8 c5 cc fa ff <0f> 0b e8 53 9b 69 f9 48 c7 c1 e0 15 9b 88 ba a5 03 00 00 48 c7 c6
RSP: 0018:ffff8880b0a97d58 EFLAGS: 00010282
RAX: 0000000000000037 RBX: ffffc90001602090 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1016152f9d
RBP: ffff8880aa01ec30 R08: 0000000000000037 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffffc90001401100 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b3132f000 CR3: 000000009d112000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
txLazyCommit fs/jfs/jfs_txnmgr.c:2727 [inline]
jfs_lazycommit+0x66b/0x9d0 fs/jfs/jfs_txnmgr.c:2777
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
---[ end trace c73519c48e9dd7fd ]---
RIP: 0010:txUnlock.cold+0x4a/0x72 fs/jfs/jfs_txnmgr.c:939
Code: eb cc fa ff 0f 0b e8 79 9b 69 f9 48 c7 c1 a0 16 9b 88 ba ab 03 00 00 48 c7 c6 20 16 9b 88 48 c7 c7 60 16 9b 88 e8 c5 cc fa ff <0f> 0b e8 53 9b 69 f9 48 c7 c1 e0 15 9b 88 ba a5 03 00 00 48 c7 c6
RSP: 0018:ffff8880b0a97d58 EFLAGS: 00010282
RAX: 0000000000000037 RBX: ffffc90001602090 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1016152f9d
RBP: ffff8880aa01ec30 R08: 0000000000000037 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffffc90001401100 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd6a09cc000 CR3: 00000000aef2d000 CR4: 00000000003406e0
EXT4-fs (loop5): mounted filesystem without journal. Opts: ,errors=continue
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
audit: type=1800 audit(1671907054.529:554): pid=4140 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor.5" name="bus" dev="loop5" ino=18 res=0
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.