[syzbot] [jfs?] kernel BUG in jfs_flush_journal (3)

1 view
Skip to first unread message

syzbot

unread,
4:09 PM (2 hours ago) 4:09 PM
to jfs-dis...@lists.sourceforge.net, linux-...@vger.kernel.org, sha...@kernel.org, syzkall...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d9d32e5bd5a4 Merge tag 'ata-7.0-rc2' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=172e80ba580000
kernel config: https://syzkaller.appspot.com/x/.config?x=70fe0401f305d8d4
dashboard link: https://syzkaller.appspot.com/bug?extid=4c8d1f29732a21567e4e
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7b88c2d85ff3/disk-d9d32e5b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/82848c6df034/vmlinux-d9d32e5b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7a552f182468/bzImage-d9d32e5b.xz

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

BUG at fs/jfs/jfs_logmgr.c:1587 assert(list_empty(&log->cqueue))
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_logmgr.c:1587!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 6732 Comm: syz.0.127 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:jfs_flush_journal+0xecd/0xef0 fs/jfs/jfs_logmgr.c:1587
Code: e9 ee f5 ff ff e8 13 cd 70 fe 48 c7 c7 40 af 8a 8b 48 c7 c6 40 aa 8a 8b ba 33 06 00 00 48 c7 c1 80 af 8a 8b e8 f4 db d3 fd 90 <0f> 0b e8 ec cc 70 fe bf 02 00 00 00 e8 52 1f 40 fe e9 10 f8 ff ff
RSP: 0018:ffffc9000f497b20 EFLAGS: 00010246
RAX: 0000000000000040 RBX: dffffc0000000000 RCX: 1239314d71958c00
RDX: ffffc9000617b000 RSI: 0000000000004dda RDI: 0000000000004ddb
RBP: ffffc9000f497c58 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff52001e92f15 R12: 00000000000000c7
R13: ffff888036268a18 R14: ffff888036268800 R15: ffff888036268ad8
FS: 00007f31648ae6c0(0000) GS:ffff888126343000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbaac7c0000 CR3: 0000000036070000 CR4: 00000000003526f0
Call Trace:
<TASK>
jfs_umount_rw+0x75/0x130 fs/jfs/jfs_umount.c:134
jfs_reconfigure+0x6f6/0xa00 fs/jfs/super.c:421
reconfigure_super+0x227/0x8a0 fs/super.c:1080
do_remount fs/namespace.c:3391 [inline]
path_mount+0xdc5/0x10e0 fs/namespace.c:4151
do_mount fs/namespace.c:4172 [inline]
__do_sys_mount fs/namespace.c:4361 [inline]
__se_sys_mount+0x31d/0x420 fs/namespace.c:4338
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f316665c629
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f31648ae028 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f31668d5fa0 RCX: 00007f316665c629
RDX: 0000000000000000 RSI: 0000200000000100 RDI: 0000000000000000
RBP: 00007f31666f2b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000021 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f31668d6038 R14: 00007f31668d5fa0 R15: 00007ffd55132e68
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:jfs_flush_journal+0xecd/0xef0 fs/jfs/jfs_logmgr.c:1587
Code: e9 ee f5 ff ff e8 13 cd 70 fe 48 c7 c7 40 af 8a 8b 48 c7 c6 40 aa 8a 8b ba 33 06 00 00 48 c7 c1 80 af 8a 8b e8 f4 db d3 fd 90 <0f> 0b e8 ec cc 70 fe bf 02 00 00 00 e8 52 1f 40 fe e9 10 f8 ff ff
RSP: 0018:ffffc9000f497b20 EFLAGS: 00010246
RAX: 0000000000000040 RBX: dffffc0000000000 RCX: 1239314d71958c00
RDX: ffffc9000617b000 RSI: 0000000000004dda RDI: 0000000000004ddb
RBP: ffffc9000f497c58 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff52001e92f15 R12: 00000000000000c7
R13: ffff888036268a18 R14: ffff888036268800 R15: ffff888036268ad8
FS: 00007f31648ae6c0(0000) GS:ffff888126343000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fbaac7c0000 CR3: 0000000036070000 CR4: 00000000003526f0


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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages