linux-kernel - [syzbot] [jfs?] kernel BUG in lbmIODone (3)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <68c33383.050a0220.2ff435.024c.GAE@google.com>
Date: Thu, 11 Sep 2025 13:39:31 -0700
From: syzbot <syzbot+a5bcc0f04f7131679010@...kaller.appspotmail.com>
To: jfs-discussion@...ts.sourceforge.net, linux-kernel@...r.kernel.org, 
	shaggy@...nel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [jfs?] kernel BUG in lbmIODone (3)

Hello,

syzbot found the following issue on:

HEAD commit:    b320789d6883 Linux 6.17-rc4
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=13ea0642580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=39f8a155475bc42d
dashboard link: https://syzkaller.appspot.com/bug?extid=a5bcc0f04f7131679010
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c497ec86c8e2/disk-b320789d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b1d08f5d7b1c/vmlinux-b320789d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4a27a997250a/Image-b320789d.gz.xz

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

BUG at fs/jfs/jfs_logmgr.c:2303 assert(bp->l_flag & lbmRELEASE)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_logmgr.c:2303!
Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP
Modules linked in:
CPU: 0 UID: 0 PID: 15 Comm: ksoftirqd/0 Not tainted syzkaller #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 634000c5 (nZCv daIF +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : lbmIODone+0x1294/0x12e8 fs/jfs/jfs_logmgr.c:2303
lr : lbmIODone+0x1294/0x12e8 fs/jfs/jfs_logmgr.c:2303
sp : ffff800097c678d0
x29: ffff800097c67960 x28: 1fffe00018c38ca1 x27: 0000000000000020
x26: 1fffe0001a4f064f x25: dfff800000000000 x24: 0000000000000000
x23: ffff0000c61c6508 x22: ffff0000d2783278 x21: 0000000000000000
x20: 0000000000000020 x19: ffff0000c61c6500 x18: 1fffe00033797688
x17: ffff80008f7de000 x16: ffff80008b00ff28 x15: 0000000000000001
x14: 1ffff00012f8ce90 x13: 0000000000000000 x12: 0000000000000000
x11: ffff700012f8ce91 x10: 0000000000ff0100 x9 : 4257e84271db6d00
x8 : 4257e84271db6d00 x7 : ffff800080563d2c x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000000 x3 : ffff8000807de8f0
x2 : 0000000000000001 x1 : 0000000100000101 x0 : 000000000000003f
Call trace:
 lbmIODone+0x1294/0x12e8 fs/jfs/jfs_logmgr.c:2303 (P)
 bio_endio+0x858/0x894 block/bio.c:1651
 blk_update_request+0x474/0xba8 block/blk-mq.c:989
 blk_mq_end_request+0x54/0x88 block/blk-mq.c:1151
 lo_complete_rq+0x124/0x274 drivers/block/loop.c:314
 blk_complete_reqs block/blk-mq.c:1226 [inline]
 blk_done_softirq+0x11c/0x168 block/blk-mq.c:1231
 handle_softirqs+0x328/0xc88 kernel/softirq.c:579
 run_ksoftirqd+0x70/0xc0 kernel/softirq.c:968
 smpboot_thread_fn+0x4d8/0x9cc kernel/smpboot.c:160
 kthread+0x5fc/0x75c kernel/kthread.c:463
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:844
Code: f004c2c3 911c0063 52811fe2 9793a804 (d4210000) 
---[ end trace 0000000000000000 ]---


---
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 syzkaller@...glegroups.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