The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+c61d6962d0b7e698439e@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	 linux-mm@kvack.org, mhocko@suse.com, rientjes@google.com,
	 shakeel.butt@linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] kernel panic: System is deadlocked on memory (2)
Date: Tue, 04 Aug 2026 07:05:36 -0700	[thread overview]
Message-ID: <6a71f1b0.40259c87.584f4.04b8.GAE@google.com> (raw)
In-Reply-To: <000000000000ac2392061f7a501b@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    848acc8ffe1b Merge tag 'fsverity-for-linus' of git://git.k..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1559b649580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=145fa60d73086782
dashboard link: https://syzkaller.appspot.com/bug?extid=c61d6962d0b7e698439e
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1531be32580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15938bb9580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-848acc8f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6fb497cc0c8d/vmlinux-848acc8f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/663ccee34982/bzImage-848acc8f.xz

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

kmalloc-96              1483KB       1500KB
kmem_cache_node          219KB        220KB
kmem_cache               181KB        226KB
Out of memory and no killable processes...
Kernel panic - not syncing: System is deadlocked on memory
CPU: 0 UID: 0 PID: 5149 Comm: udevd Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 vpanic+0x552/0x970 kernel/panic.c:651
 panic+0xd1/0xe0 kernel/panic.c:788
 out_of_memory.cold+0xa2/0x170 mm/oom_kill.c:1166
 __alloc_pages_may_oom mm/page_alloc.c:4116 [inline]
 __alloc_pages_slowpath mm/page_alloc.c:4967 [inline]
 __alloc_frozen_pages_noprof+0x24c2/0x2dc0 mm/page_alloc.c:5317
 alloc_pages_mpol+0x1fb/0x540 mm/mempolicy.c:2490
 alloc_pages_noprof mm/mempolicy.c:2581 [inline]
 folio_alloc_noprof+0x22/0x250 mm/mempolicy.c:2591
 filemap_alloc_folio_noprof.part.0+0x377/0x450 mm/filemap.c:1013
 filemap_alloc_folio_noprof mm/filemap.c:2027 [inline]
 __filemap_get_folio_mpol+0x653/0x1320 mm/filemap.c:2012
 __filemap_get_folio include/linux/pagemap.h:761 [inline]
 filemap_fault+0x879/0x3130 mm/filemap.c:3592
 __do_fault+0x10b/0x440 mm/memory.c:5425
 do_read_fault mm/memory.c:5860 [inline]
 do_fault+0xa99/0x1750 mm/memory.c:5994
 do_pte_missing mm/memory.c:4566 [inline]
 handle_pte_fault mm/memory.c:6379 [inline]
 __handle_mm_fault+0x187d/0x2a00 mm/memory.c:6517
 handle_mm_fault+0x37b/0xa30 mm/memory.c:6686
 do_user_addr_fault+0x5a3/0x12f0 arch/x86/mm/fault.c:1343
 handle_page_fault arch/x86/mm/fault.c:1483 [inline]
 exc_page_fault+0x6f/0xd0 arch/x86/mm/fault.c:1536
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595
RIP: 0033:0x7f72d08a7407
Code: Unable to access opcode bytes at 0x7f72d08a73dd.
RSP: 002b:00007ffff9fa8a10 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 00007f72d1003880 RCX: 00007f72d08a7407
RDX: 0000000000000008 RSI: 00007ffff9fa8b70 RDI: 000000000000000b
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000bb8 R11: 0000000000000202 R12: 0000000000000000
R13: 0000558259d38100 R14: 0000000000000001 R15: 00007ffff9fa8c60
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

      reply	other threads:[~2026-08-04 14:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 10:54 [syzbot] [mm?] kernel panic: System is deadlocked on memory (2) syzbot
2026-08-04 14:05 ` syzbot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a71f1b0.40259c87.584f4.04b8.GAE@google.com \
    --to=syzbot+c61d6962d0b7e698439e@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=rientjes@google.com \
    --cc=shakeel.butt@linux.dev \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox