[v5.15] BUG: Bad page state in diRead

0 views
Skip to first unread message

syzbot

unread,
Apr 1, 2026, 9:31:29 AM (4 days ago) Apr 1
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1087ed02580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=859c6ff3eba5b1175c02
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/74e75dfcb812/disk-91d48252.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz

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

BUG: Bad page state in process jfsCommit pfn:1f3f5
page:ffffea00007cfd40 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1c pfn:0x1f3f5
raw: 000000000000001c ffff88804fe7eaa8 00000000ffffffff 0000000000000000
page dumped because: PAGE_FLAGS_CHECK_AT_FREE flag(s) set
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x100c40(GFP_NOFS|__GFP_HARDWALL), pid 8859, ts 205941531317, free_ts 203867491702
prep_new_page mm/page_alloc.c:2426 [inline]
get_page_from_freelist+0x1bbd/0x1ca0 mm/page_alloc.c:4192
__alloc_pages+0x1ee/0x480 mm/page_alloc.c:5501
__page_cache_alloc+0xce/0x440 mm/filemap.c:1022
do_read_cache_page+0x1da/0x1030 mm/filemap.c:3457
diRead+0x6f7/0xbb0 fs/jfs/jfs_imap.c:367
jfs_iget+0x89/0x3f0 fs/jfs/inode.c:35
jfs_fill_super+0x73b/0xb00 fs/jfs/super.c:585
mount_bdev+0x287/0x3c0 fs/super.c:1400
legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x24a/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1340 [inline]
free_pcp_prepare mm/page_alloc.c:1391 [inline]
free_unref_page_prepare+0x637/0x6c0 mm/page_alloc.c:3317
free_unref_page+0x8f/0x2a0 mm/page_alloc.c:3396
qlist_free_all+0x35/0x90 mm/kasan/quarantine.c:176
kasan_quarantine_reduce+0x150/0x160 mm/kasan/quarantine.c:283
__kasan_slab_alloc+0x2f/0xd0 mm/kasan/common.c:444
kasan_slab_alloc include/linux/kasan.h:254 [inline]
slab_post_alloc_hook+0x4c/0x380 mm/slab.h:519
slab_alloc_node mm/slub.c:3225 [inline]
slab_alloc mm/slub.c:3233 [inline]
kmem_cache_alloc+0x100/0x290 mm/slub.c:3238
sock_alloc_inode+0x17/0xb0 net/socket.c:305
alloc_inode fs/inode.c:261 [inline]
new_inode_pseudo+0x5f/0x210 fs/inode.c:1001
sock_alloc net/socket.c:628 [inline]
do_accept+0x197/0x6f0 net/socket.c:1788
__sys_accept4_file net/socket.c:1852 [inline]
__sys_accept4+0x103/0x170 net/socket.c:1882
__do_sys_accept4 net/socket.c:1894 [inline]
__se_sys_accept4 net/socket.c:1891 [inline]
__x64_sys_accept4+0x96/0xb0 net/socket.c:1891
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
Modules linked in:
CPU: 1 PID: 277 Comm: jfsCommit Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
bad_page+0x14b/0x170 mm/page_alloc.c:652
check_free_page mm/page_alloc.c:1209 [inline]
free_pages_prepare mm/page_alloc.c:1334 [inline]
free_pcp_prepare mm/page_alloc.c:1391 [inline]
free_unref_page_prepare+0x383/0x6c0 mm/page_alloc.c:3317
free_unref_page+0x8f/0x2a0 mm/page_alloc.c:3396
txUnlock+0x27e/0xcb0 fs/jfs/jfs_txnmgr.c:933
txLazyCommit fs/jfs/jfs_txnmgr.c:2717 [inline]
jfs_lazycommit+0x581/0xb40 fs/jfs/jfs_txnmgr.c:2767
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
page:ffffea00007cfd40 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1c pfn:0x1f3f5
flags: 0xfff00000002007(locked|referenced|uptodate|private|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000002007 dead000000000100 dead000000000122 0000000000000000
raw: 000000000000001c ffff88804fe7eaa8 00000000ffffffff 0000000000000000
page dumped because: VM_BUG_ON_PAGE(((unsigned int) page_ref_count(page) + 127u <= 127u))
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x100c40(GFP_NOFS|__GFP_HARDWALL), pid 8859, ts 205941531317, free_ts 203867491702
prep_new_page mm/page_alloc.c:2426 [inline]
get_page_from_freelist+0x1bbd/0x1ca0 mm/page_alloc.c:4192
__alloc_pages+0x1ee/0x480 mm/page_alloc.c:5501
__page_cache_alloc+0xce/0x440 mm/filemap.c:1022
do_read_cache_page+0x1da/0x1030 mm/filemap.c:3457
read_mapping_page include/linux/pagemap.h:515 [inline]
__get_metapage+0x35d/0x1060 fs/jfs/jfs_metapage.c:621
diRead+0x6f7/0xbb0 fs/jfs/jfs_imap.c:367
jfs_iget+0x89/0x3f0 fs/jfs/inode.c:35
jfs_fill_super+0x73b/0xb00 fs/jfs/super.c:585
mount_bdev+0x287/0x3c0 fs/super.c:1400
legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x24a/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1340 [inline]
free_pcp_prepare mm/page_alloc.c:1391 [inline]
free_unref_page_prepare+0x637/0x6c0 mm/page_alloc.c:3317
free_unref_page+0x8f/0x2a0 mm/page_alloc.c:3396
qlist_free_all+0x35/0x90 mm/kasan/quarantine.c:176
kasan_quarantine_reduce+0x150/0x160 mm/kasan/quarantine.c:283
__kasan_slab_alloc+0x2f/0xd0 mm/kasan/common.c:444
kasan_slab_alloc include/linux/kasan.h:254 [inline]
slab_post_alloc_hook+0x4c/0x380 mm/slab.h:519
slab_alloc_node mm/slub.c:3225 [inline]
slab_alloc mm/slub.c:3233 [inline]
kmem_cache_alloc+0x100/0x290 mm/slub.c:3238
sock_alloc_inode+0x17/0xb0 net/socket.c:305
alloc_inode fs/inode.c:261 [inline]
new_inode_pseudo+0x5f/0x210 fs/inode.c:1001
sock_alloc net/socket.c:628 [inline]
do_accept+0x197/0x6f0 net/socket.c:1788
__sys_accept4_file net/socket.c:1852 [inline]
__sys_accept4+0x103/0x170 net/socket.c:1882
__do_sys_accept4 net/socket.c:1894 [inline]
__se_sys_accept4 net/socket.c:1891 [inline]
__x64_sys_accept4+0x96/0xb0 net/socket.c:1891
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
------------[ cut here ]------------
kernel BUG at include/linux/mm.h:1224!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 277 Comm: jfsCommit Tainted: G B syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:get_page include/linux/mm.h:1224 [inline]
RIP: 0010:put_metapage+0x278/0x280 fs/jfs/jfs_metapage.c:722
Code: 38 c1 0f 8c 00 ff ff ff 4c 89 ef e8 42 b9 ec fe e9 f3 fe ff ff e8 e8 ad a7 fe 48 8b 3c 24 48 c7 c6 a0 54 62 8a e8 c8 93 da fe <0f> 0b 66 0f 1f 44 00 00 55 41 57 41 56 41 55 41 54 53 48 83 ec 70
RSP: 0018:ffffc90002d6fce0 EFLAGS: 00010246
RAX: 849b9abcb3636e00 RBX: ffff88804fe7eaa8 RCX: 0000000000000000
RDX: 0000000000000044 RSI: 0000000000000000 RDI: fffff520005adf90
RBP: 000000000000007f R08: ffff8880b9133d7f R09: fffff520005adf4c
R10: dffffc0000000000 R11: ffffed10172267b0 R12: ffff88804fe7ead0
R13: ffffea00007cfd74 R14: 1ffff11009fcfd5a R15: 1ffff11009fcfd67
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0a417404f2 CR3: 0000000074113000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
txUnlock+0x427/0xcb0 fs/jfs/jfs_txnmgr.c:948
txLazyCommit fs/jfs/jfs_txnmgr.c:2717 [inline]
jfs_lazycommit+0x581/0xb40 fs/jfs/jfs_txnmgr.c:2767
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace aa3386d6859e6120 ]---
RIP: 0010:get_page include/linux/mm.h:1224 [inline]
RIP: 0010:put_metapage+0x278/0x280 fs/jfs/jfs_metapage.c:722
Code: 38 c1 0f 8c 00 ff ff ff 4c 89 ef e8 42 b9 ec fe e9 f3 fe ff ff e8 e8 ad a7 fe 48 8b 3c 24 48 c7 c6 a0 54 62 8a e8 c8 93 da fe <0f> 0b 66 0f 1f 44 00 00 55 41 57 41 56 41 55 41 54 53 48 83 ec 70
RSP: 0018:ffffc90002d6fce0 EFLAGS: 00010246
RAX: 849b9abcb3636e00 RBX: ffff88804fe7eaa8 RCX: 0000000000000000
RDX: 0000000000000044 RSI: 0000000000000000 RDI: fffff520005adf90
RBP: 000000000000007f R08: ffff8880b9133d7f R09: fffff520005adf4c
R10: dffffc0000000000 R11: ffffed10172267b0 R12: ffff88804fe7ead0
R13: ffffea00007cfd74 R14: 1ffff11009fcfd5a R15: 1ffff11009fcfd67
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
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.

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