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

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: <67aa996b.050a0220.3d72c.0057.GAE@google.com>
Date: Mon, 10 Feb 2025 16:27:23 -0800
From: syzbot <syzbot+856d1897cd91a6a435c9@...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 (2)

Hello,

syzbot found the following issue on:

HEAD commit:    2014c95afece Linux 6.14-rc1
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=10e40b18580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b8a65ac161350c5e
dashboard link: https://syzkaller.appspot.com/bug?extid=856d1897cd91a6a435c9
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c767824b323f/disk-2014c95a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/81289e194973/vmlinux-2014c95a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4a33d49982f5/Image-2014c95a.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+856d1897cd91a6a435c9@...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] PREEMPT SMP
Modules linked in:
CPU: 0 UID: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.14.0-rc1-syzkaller-g2014c95afece #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : lbmIODone+0x12c4/0x1318 fs/jfs/jfs_logmgr.c:2303
lr : lbmIODone+0x12c4/0x1318 fs/jfs/jfs_logmgr.c:2303
sp : ffff800097d778f0
x29: ffff800097d77980 x28: 1fffe0001b405141 x27: 1ffff00012037934
x26: 1fffe0001e20724f x25: dfff800000000000 x24: 0000000000000000
x23: ffff0000da028a08 x22: 0000000000000000 x21: 0000000000000000
x20: 0000000000000020 x19: ffff0000da028a00 x18: 0000000000000008
x17: 0000000000000000 x16: ffff8000832d977c x15: 0000000000000001
x14: 1ffff00012faee78 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000000102 x10: 0000000000ff0100 x9 : ac6013805dc83c00
x8 : ac6013805dc83c00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff800097d770b8 x4 : ffff80008fcbefc0 x3 : ffff800083275f78
x2 : 0000000000000001 x1 : 0000000100000101 x0 : 000000000000003f
Call trace:
 lbmIODone+0x12c4/0x1318 fs/jfs/jfs_logmgr.c:2303 (P)
 bio_endio+0x840/0x87c block/bio.c:1548
 blk_update_request+0x4ac/0xda0 block/blk-mq.c:983
 blk_mq_end_request+0x54/0x88 block/blk-mq.c:1145
 lo_complete_rq+0x188/0x2f4 drivers/block/loop.c:395
 blk_complete_reqs block/blk-mq.c:1220 [inline]
 blk_done_softirq+0x11c/0x168 block/blk-mq.c:1225
 handle_softirqs+0x320/0xd34 kernel/softirq.c:561
 run_ksoftirqd+0x70/0xc0 kernel/softirq.c:950
 smpboot_thread_fn+0x4b0/0x90c kernel/smpboot.c:164
 kthread+0x65c/0x7b0 kernel/kthread.c:464
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862
Code: d004fd63 91188063 52811fe2 979153a6 (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