From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f80.google.com (mail-oo1-f80.google.com [209.85.161.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7D72330C615 for ; Sun, 3 May 2026 11:47:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.80 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777808849; cv=none; b=q21gif05/cqMlGNhhfp6OB5vkaCQDOMi3BmNG6DKdJU4q1gpJVx7AIN8VGIt0J6h2mhvhl6td2hqULVTN0mCeAnFeih2toUgezt3U6mYTX0Oyvbheq8v7uCn5YoJiTxikDX/OZxd5OjdJDALs/TfZg22GVAF9aFDwkOQ6u0nIOk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777808849; c=relaxed/simple; bh=kqO8ZAvKFFXVjoT8MwZsVYguNVVSLtEAwwSUMbgqoEw=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=theprsnvla6Ppks89WV+DyxHxCSSsyKOqlC/bLiQ/JzdJWJ2zzX9qdO16+dOLEE5iRKK3UUssydCdJCBihkij7ayEfUHxscF2ojZoc6dBkuHHUR1L+IkC+JNEtoa1ekp48RIOv16V2v1JBapzkQmaFwi6au3RIBGs8sJQ703Ulo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.161.80 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oo1-f80.google.com with SMTP id 006d021491bc7-69492bc3a38so4171962eaf.3 for ; Sun, 03 May 2026 04:47:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1777808846; x=1778413646; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=XzAAI/ptUzx8XTD2iRvyBhOM1/obDCx04Mkukv6AGf0=; b=D/sLMMir2PLcR89vjkjOYKCVsVpjYkKiDFLnPvmSKE+OR0CfUq9EdsObtvDDUeARhS IrIFYqIDWmkb0pxsW+RZ2A/WRtckeYI0oCRaNBvEvfyEI5Q55oAIqvvaeW30DgzWfi1b GfRZsSMEZhOiHuQfJ8ltrqI8oaFc5shAQ7j8Bg3WEcn/L0JE+nCzIXkd1hILcCraX8bD LN8ccRj7Rn3R3zOUpA9bW7kPR7AHDXsdjIU/ISreVLJaG8u5Rs4W4ioUtM+ZZIxlbvK9 9NCHtvWtU4NL9EJ8MQG3tRCNmtmUYTtQlMhC3NjttwE9MysrO7ENHkj3T4xEqIPveeCV M28g== X-Forwarded-Encrypted: i=1; AFNElJ/TzumzUP1I2qSijLiP4EAso8fDN3xQLJi71aW7TfKYs/EhamzR7EsKYLQ4a/BVRTwk1/Fr6aP0Ogl5gSk=@vger.kernel.org X-Gm-Message-State: AOJu0YzG+oPDb9VP2NC3ae8ikYJJ8mM5mkgsm4cBF7SLbRCdMzxIIO7S Pfs/gQKHm13HhoKXJHippxd6+qLl4ogej18Fax4BSZW1NnCAd5GKwGCYkLncAX0fnlw+jUsnPrc s454fVIBzhk5aYhhkGgFwOLP8OXIMdvltOjMjHTsaRmmoJw66zXtZGt+tPI4= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:f031:b0:694:9afd:7607 with SMTP id 006d021491bc7-696979cbe93mr2853690eaf.14.1777808846497; Sun, 03 May 2026 04:47:26 -0700 (PDT) Date: Sun, 03 May 2026 04:47:26 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69f735ce.050a0220.312cd3.0031.GAE@google.com> Subject: [syzbot] [mm?] BUG: sleeping function called from invalid context in vma_alloc_folio_noprof (2) From: syzbot To: Liam.Howlett@oracle.com, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org, shakeel.butt@linux.dev, surenb@google.com, syzkaller-bugs@googlegroups.com, vbabka@kernel.org Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: dca922e019dd Merge tag 'xsa48x-7.1-tag' of git://git.kerne.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=100242ce580000 kernel config: https://syzkaller.appspot.com/x/.config?x=d0f0911eedbc130a dashboard link: https://syzkaller.appspot.com/bug?extid=a21650c1666eae7b2aae compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 userspace arch: i386 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-dca922e0.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/1e719cb224ff/vmlinux-dca922e0.xz kernel image: https://storage.googleapis.com/syzbot-assets/79a541b03a9e/bzImage-dca922e0.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+a21650c1666eae7b2aae@syzkaller.appspotmail.com BUG: sleeping function called from invalid context at ./include/linux/sched/mm.h:323 in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 5665, name: dhcpcd-run-hook preempt_count: 0, expected: 0 RCU nest depth: 1, expected: 0 2 locks held by dhcpcd-run-hook/5665: #0: ffff8880243d01c8 (vm_lock){++++}-{0:0}, at: lock_vma_under_rcu+0x11d/0x590 mm/mmap_lock.c:310 #1: ffffffff8e7e52e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline] #1: ffffffff8e7e52e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline] #1: ffffffff8e7e52e0 (rcu_read_lock){....}-{1:3}, at: __pte_offset_map+0x2f/0x310 mm/pgtable-generic.c:290 CPU: 0 UID: 0 PID: 5665 Comm: dhcpcd-run-hook 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: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120 __might_resched.cold+0x1ec/0x232 kernel/sched/core.c:9162 might_alloc include/linux/sched/mm.h:323 [inline] prepare_alloc_pages+0x44a/0x5f0 mm/page_alloc.c:4995 __alloc_frozen_pages_noprof+0x19a/0x2bc0 mm/page_alloc.c:5215 alloc_pages_mpol+0x1fb/0x540 mm/mempolicy.c:2490 folio_alloc_mpol_noprof+0x36/0x260 mm/mempolicy.c:2509 vma_alloc_folio_noprof+0xed/0x1d0 mm/mempolicy.c:2544 folio_prealloc mm/memory.c:1193 [inline] wp_page_copy mm/memory.c:3859 [inline] do_wp_page+0x1ee1/0x4350 mm/memory.c:4320 handle_pte_fault mm/memory.c:6427 [inline] __handle_mm_fault+0x1ab6/0x2a00 mm/memory.c:6549 handle_mm_fault+0x36d/0xa20 mm/memory.c:6718 do_user_addr_fault+0x5a3/0x12f0 arch/x86/mm/fault.c:1334 handle_page_fault arch/x86/mm/fault.c:1474 [inline] exc_page_fault+0x6f/0xd0 arch/x86/mm/fault.c:1527 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618 RIP: 0033:0x7f5a6f60980e Code: df e8 d7 c4 ff ff 48 8d 3d 9c 92 05 00 31 c0 e8 e1 ca ff ff 95 75 24 48 8d 05 5e 9c 07 00 44 89 f2 4c 89 e6 48 89 df 48 8b 00 <83> a0 f8 02 00 00 00 e8 de eb ff ff e9 a8 00 00 00 48 85 db 0f 84 RSP: 002b:00007ffc0b5c63f0 EFLAGS: 00010246 RAX: 000055c4ea134910 RBX: 000055c4ea135c60 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 000055c4ea138c30 RDI: 000055c4ea135c60 RBP: 0000000000000000 R08: 00007f5a6f5b4b60 R09: 0000000000000000 R10: 0000000000000008 R11: 0000000000000246 R12: 000055c4ea138c30 R13: 000055c4ea135c60 R14: 0000000000000000 R15: 0000000000000000 ================================================ WARNING: lock held when returning to user space! syzkaller #0 Tainted: G W ------------------------------------------------ dhcpcd-run-hook/5665 is leaving the kernel with locks still held! 1 lock held by dhcpcd-run-hook/5665: #0: ffffffff8e7e52e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline] #0: ffffffff8e7e52e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline] #0: ffffffff8e7e52e0 (rcu_read_lock){....}-{1:3}, at: __pte_offset_map+0x2f/0x310 mm/pgtable-generic.c:290 --- 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@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