Hello,
syzbot found the following issue on:
HEAD commit: dc5c83b7f5f8 Linux 6.1.178
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=105b909e580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link:
https://syzkaller.appspot.com/bug?extid=9467e600602a876a459c
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/a9aa438e39c2/disk-dc5c83b7.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/a7b5afd2e170/vmlinux-dc5c83b7.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/3c7673d370fb/bzImage-dc5c83b7.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+9467e6...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3600 at mm/page_alloc.c:4526 __alloc_pages_may_oom mm/page_alloc.c:4526 [inline]
WARNING: CPU: 1 PID: 3600 at mm/page_alloc.c:4526 __alloc_pages_slowpath+0x1b6e/0x2290 mm/page_alloc.c:5333
Modules linked in:
CPU: 1 PID: 3600 Comm: jbd2/sda1-8 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
RIP: 0010:__alloc_pages_may_oom mm/page_alloc.c:4526 [inline]
RIP: 0010:__alloc_pages_slowpath+0x1b6e/0x2290 mm/page_alloc.c:5333
Code: e9 ad ee ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c ff ee ff ff 4c 89 f7 e8 5e 1d 0b 00 e9 f2 ee ff ff c6 05 8a 5c 44 0c 01 <0f> 0b 66 83 7c 24 04 00 0f 89 bd fb ff ff 8b 7c 24 04 8b 1c 24 89
RSP: 0018:ffffc9000e5bf2c0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 8ad46b4c97c72600
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffc9000e5bf440
RBP: ffffc9000e5bf510 R08: ffff88823fff8497 R09: 1ffff11047fff092
R10: dffffc0000000000 R11: ffffed1047fff093 R12: 0000000000000000
R13: 0000000000000011 R14: 0000000000000001 R15: ffffc9000e5bf568
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055557c0cc7d0 CR3: 000000000c88e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__alloc_pages+0x346/0x4f0 mm/page_alloc.c:5671
folio_alloc+0x1c/0x60 mm/mempolicy.c:2292
filemap_alloc_folio+0xdb/0x480 mm/filemap.c:999
__filemap_get_folio+0x6ba/0xde0 mm/filemap.c:1993
pagecache_get_page+0x26/0x260 mm/folio-compat.c:110
find_or_create_page include/linux/pagemap.h:648 [inline]
grow_dev_page fs/buffer.c:946 [inline]
grow_buffers fs/buffer.c:1011 [inline]
__getblk_slow fs/buffer.c:1038 [inline]
__getblk_gfp+0x2a0/0xa80 fs/buffer.c:1333
__getblk include/linux/buffer_head.h:411 [inline]
jbd2_journal_get_descriptor_buffer+0xcd/0x360 fs/jbd2/journal.c:1023
jbd2_journal_commit_transaction+0x13fd/0x5f30 fs/jbd2/commit.c:645
kjournald2+0x40b/0x800 fs/jbd2/journal.c:210
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
---
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