kernel BUG at fs/jfs/jfs_logmgr.c:LINE!

5 views
Skip to first unread message

syzbot

unread,
Nov 11, 2020, 4:07:20 AM11/11/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 31acccdc Linux 4.19.157
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15d4ffb2500000
kernel config: https://syzkaller.appspot.com/x/.config?x=1f604e014c43fe09
dashboard link: https://syzkaller.appspot.com/bug?extid=01c9c0e73a9533a0afa5
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+01c9c0...@syzkaller.appspotmail.com

BUG at fs/jfs/jfs_logmgr.c:2325 assert(bp->l_flag & lbmRELEASE)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_logmgr.c:2325!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 14682 Comm: loop1 Not tainted 4.19.157-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:lbmIODone.cold+0x24/0x5b fs/jfs/jfs_logmgr.c:2325
Code: ff e8 cb ff ff ff e8 fb 82 e6 fe 48 c7 c1 00 eb 9a 88 ba 15 09 00 00 48 c7 c6 80 ea 9a 88 48 c7 c7 c0 ea 9a 88 e8 8b 7c d1 fe <0f> 0b e8 d5 82 e6 fe 48 c7 c1 40 eb 9a 88 ba 16 09 00 00 48 c7 c6
RSP: 0018:ffff888058b87ac0 EFLAGS: 00010086
RAX: 000000000000003f RBX: ffff8880980fd000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814fdb21 RDI: ffffed100b170f4a
RBP: 0000000000000020 R08: 000000000000003f R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000286
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000016a5374 CR3: 000000008ae0a000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
bio_endio+0x471/0x810 block/bio.c:1780
req_bio_endio block/blk-core.c:278 [inline]
blk_update_request+0x30f/0xaf0 block/blk-core.c:3111
blk_mq_end_request+0x4a/0x340 block/blk-mq.c:544
lo_complete_rq+0x201/0x2d0 drivers/block/loop.c:487
__blk_mq_complete_request block/blk-mq.c:583 [inline]
blk_mq_complete_request+0x472/0x660 block/blk-mq.c:620
loop_handle_cmd drivers/block/loop.c:1931 [inline]
loop_queue_work+0x274/0x20c0 drivers/block/loop.c:1940
kthread_worker_fn+0x292/0x730 kernel/kthread.c:675
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
---[ end trace 242c423e583706f1 ]---
RIP: 0010:lbmIODone.cold+0x24/0x5b fs/jfs/jfs_logmgr.c:2325
Code: ff e8 cb ff ff ff e8 fb 82 e6 fe 48 c7 c1 00 eb 9a 88 ba 15 09 00 00 48 c7 c6 80 ea 9a 88 48 c7 c7 c0 ea 9a 88 e8 8b 7c d1 fe <0f> 0b e8 d5 82 e6 fe 48 c7 c1 40 eb 9a 88 ba 16 09 00 00 48 c7 c6
RSP: 0018:ffff888058b87ac0 EFLAGS: 00010086
RAX: 000000000000003f RBX: ffff8880980fd000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814fdb21 RDI: ffffed100b170f4a
RBP: 0000000000000020 R08: 000000000000003f R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000286
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000016a5374 CR3: 000000008ae0a000 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

unread,
Oct 3, 2022, 6:03:39 AM10/3/22
to syzkaller...@googlegroups.com
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=164a17c0880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=01c9c0e73a9533a0afa5
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14754b98880000

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+01c9c0...@syzkaller.appspotmail.com

BUG at fs/jfs/jfs_logmgr.c:2326 assert(bp->l_flag & lbmRELEASE)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_logmgr.c:2326!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 913 Comm: loop0 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
RIP: 0010:lbmIODone.cold+0x24/0x5b fs/jfs/jfs_logmgr.c:2326
Code: f9 e8 cb ff ff ff e8 47 9c 69 f9 48 c7 c1 80 11 9b 88 ba 16 09 00 00 48 c7 c6 00 11 9b 88 48 c7 c7 40 11 9b 88 e8 93 cd fa ff <0f> 0b e8 21 9c 69 f9 48 c7 c1 c0 11 9b 88 ba 17 09 00 00 48 c7 c6
RSP: 0018:ffff888096507ac0 EFLAGS: 00010086
RAX: 000000000000003f RBX: ffff8880b520ef00 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1012ca0f4a
RBP: 0000000000000020 R08: 000000000000003f R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000286
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8fcfbe40b0 CR3: 000000009103a000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
bio_endio+0x488/0x830 block/bio.c:1780
req_bio_endio block/blk-core.c:278 [inline]
blk_update_request+0x30f/0xaf0 block/blk-core.c:3112
blk_mq_end_request+0x4a/0x340 block/blk-mq.c:544
lo_complete_rq+0x201/0x2d0 drivers/block/loop.c:487
__blk_mq_complete_request block/blk-mq.c:583 [inline]
blk_mq_complete_request+0x472/0x660 block/blk-mq.c:620
loop_handle_cmd drivers/block/loop.c:1931 [inline]
loop_queue_work+0x274/0x20c0 drivers/block/loop.c:1940
kthread_worker_fn+0x292/0x730 kernel/kthread.c:700
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
---[ end trace b63e4b8bedc38bf8 ]---
RIP: 0010:lbmIODone.cold+0x24/0x5b fs/jfs/jfs_logmgr.c:2326
Code: f9 e8 cb ff ff ff e8 47 9c 69 f9 48 c7 c1 80 11 9b 88 ba 16 09 00 00 48 c7 c6 00 11 9b 88 48 c7 c7 40 11 9b 88 e8 93 cd fa ff <0f> 0b e8 21 9c 69 f9 48 c7 c1 c0 11 9b 88 ba 17 09 00 00 48 c7 c6
RSP: 0018:ffff888096507ac0 EFLAGS: 00010086
RAX: 000000000000003f RBX: ffff8880b520ef00 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1012ca0f4a
RBP: 0000000000000020 R08: 000000000000003f R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000286
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8fcfbe40b0 CR3: 000000009103a000 CR4: 00000000003406f0
Reply all
Reply to author
Forward
0 new messages