From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f207.google.com (mail-oi1-f207.google.com [209.85.167.207]) (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 9DBCF364927 for ; Sat, 1 Aug 2026 00:36:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.207 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785544605; cv=none; b=JKqvNKzUbUSM9oAelWtBPL/DXLFO8/PCy5hzirBHyv3+HyuR7hmoMbe59G6bOkuLMzKqOGgigkXTeISvyQYvVN895SlvYbsnScivI49NvveD9R3Fepo0QudPTkz8hCskNyHeOGipOkLeEMjeQyxF65AsM0cgfRUUGhN6RDkSdCs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785544605; c=relaxed/simple; bh=D8+j0ktfb036FfbSMOlKmhOCZ0FbHGZCSRqv/VOj0PQ=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=uID4OSsIfp1QdSkASSBotUd1N/5TCA4WHEjlLggN2xBP26H7OluhSoFmEprCypyO49CSqzj49dYBNfiLZj3Kx06lAjQFtKnr+zLySOk7rbF4hVuOy3/4qVOcuLBVFGDULYFCUeleJqOcx2GiUgYJfFF2qdH79GBFbhyto6XZJlQ= 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.167.207 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-oi1-f207.google.com with SMTP id 5614622812f47-48e5de5a23cso911689b6e.0 for ; Fri, 31 Jul 2026 17:36:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1785544601; x=1786149401; h=content-type:to:from:subject:message-id:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=FUoHlSVYyRWQcZ6/7tjmj01mDGscNWRNSzyTEDtffAc=; b=dW4xlRjnYX3fvB8syD5wbG79RuhuQ6bAs2IhasZFs7mFekLcDfJAinqHfEO8CK9bi9 fGC8z9f9f9d1QKyAz4Ko5LFmh9hoCEhV3o84O6nvq7F+EVAK4A19/3Ye4rOPt6vQZ8hh Rfjf3+GBWaBoLwu/Mkio1XIsNcKlQ0OBPPNWxkDKzga2IsnI2GzVtD6rHZSOHb0/MUxB BZXwHBbgpV/ZdAQ+hf7AKPxpfHk0bBQGEU+6soXd8wr3cvt1jdDvhEeW62siNvStjL1/ +2IZu+TV8TLSpve3gDsk3QjwR2DMZGKuc1tu2oDeupuIxE2faRcpcC0LU0hPpgpfkNn5 6Mhg== X-Forwarded-Encrypted: i=1; AHgh+Rrhv34cdpZfNrMHjRfOBxo5daS+GEBmBoWwphjt5ZJU+qMx9sazzEQQnhC5g+GdLpXxyZucCCYdHGXKASc=@vger.kernel.org X-Gm-Message-State: AOJu0Yz/AhSAsP+834iENRTEf5PvrQbE3Q8QDhTW2a/ar6a/x5tzye5q jjC7CnbRni661Izl0ZWTPgeW806ZAYpBZU4kTU4N4TRiMYtVKFlnM6eGtJadcFTQx3uhAXX1GIk kpy97x2s6Ur0U3yzHqt9c1IEIui+TyQksuEzhFZzO49WazuwP82BnLkuJuIY= 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:6808:1484:b0:48a:ddd4:d36f with SMTP id 5614622812f47-4af5e0c2e55mr3930519b6e.8.1785544601341; Fri, 31 Jul 2026 17:36:41 -0700 (PDT) Date: Fri, 31 Jul 2026 17:36:41 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a6d3f99.13bfb6d0.1ecdd5.0255.GAE@google.com> Subject: [syzbot] [mm?] WARNING in alloc_vmap_area From: syzbot To: akpm@linux-foundation.org, bsegall@google.com, david@kernel.org, dietmar.eggemann@arm.com, juri.lelli@redhat.com, kees@kernel.org, kprateek.nayak@amd.com, liam@infradead.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org, mgorman@suse.de, mhocko@suse.com, mingo@redhat.com, peterz@infradead.org, rostedt@goodmis.org, rppt@kernel.org, surenb@google.com, syzkaller-bugs@googlegroups.com, vbabka@kernel.org, vincent.guittot@linaro.org, vschneid@redhat.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 11028ab62899 Merge tag 'probes-fixes-v7.2-rc5' of git://gi.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=165f9499580000 kernel config: https://syzkaller.appspot.com/x/.config?x=f221a1b5d497ed15 dashboard link: https://syzkaller.appspot.com/bug?extid=a308ee836af04d1d6fa6 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-11028ab6.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/50d1387eb51d/vmlinux-11028ab6.xz kernel image: https://storage.googleapis.com/syzbot-assets/30ffbd0f8cd4/bzImage-11028ab6.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+a308ee836af04d1d6fa6@syzkaller.appspotmail.com ret WARNING: mm/vmalloc.c:1820 at va_alloc mm/vmalloc.c:1820 [inline], CPU#3: kworker/u33:7/821 WARNING: mm/vmalloc.c:1820 at __alloc_vmap_area mm/vmalloc.c:1855 [inline], CPU#3: kworker/u33:7/821 WARNING: mm/vmalloc.c:1820 at alloc_vmap_area+0x17f6/0x2bb0 mm/vmalloc.c:2073, CPU#3: kworker/u33:7/821 Modules linked in: CPU: 3 UID: 0 PID: 821 Comm: kworker/u33:7 Tainted: G S syzkaller #0 PREEMPT(full) Tainted: [S]=CPU_OUT_OF_SPEC Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Workqueue: events_unbound call_usermodehelper_exec_work RIP: 0010:va_alloc mm/vmalloc.c:1820 [inline] RIP: 0010:__alloc_vmap_area mm/vmalloc.c:1855 [inline] RIP: 0010:alloc_vmap_area+0x17f6/0x2bb0 mm/vmalloc.c:2073 Code: 48 8d 3d 8d d8 c0 0e 8b 74 24 10 67 48 0f b9 3a c7 44 24 70 00 00 00 00 e9 95 ed ff ff 48 c7 c3 ea ff ff ff e8 7b b0 a2 ff 90 <0f> 0b 90 41 be 01 00 00 00 e9 ae f9 ff ff 41 be 01 00 00 00 48 c7 RSP: 0018:ffffc90004627458 EFLAGS: 00010293 RAX: 0000000000000000 RBX: fffffffffffffff4 RCX: 0000000000002800 RDX: ffff888025aa8000 RSI: ffffffff8266fbe5 RDI: ffffffff8e46c938 RBP: ffffc90003389000 R08: 00000000ffffffff R09: fffffbfff1dbda96 R10: ffffffff8eded4b3 R11: 0000000000000000 R12: 0000000000000000 R13: ffffc90003399000 R14: ffffe8ffffffffff R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff888096ee3000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000f7f3a190 CR3: 000000002228f000 CR4: 0000000000352ef0 Call Trace: __get_vm_area_node+0x1ca/0x330 mm/vmalloc.c:3226 __vmalloc_node_range_noprof+0x228/0x1630 mm/vmalloc.c:4042 __vmalloc_node_noprof+0xad/0xf0 mm/vmalloc.c:4143 alloc_thread_stack_node kernel/fork.c:359 [inline] dup_task_struct kernel/fork.c:929 [inline] copy_process+0x7fb/0x8030 kernel/fork.c:2115 kernel_clone+0x176/0x9d0 kernel/fork.c:2748 user_mode_thread+0xcc/0x110 kernel/fork.c:2824 call_usermodehelper_exec_sync kernel/umh.c:132 [inline] call_usermodehelper_exec_work+0x6b/0x180 kernel/umh.c:163 process_one_work+0xa23/0x1940 kernel/workqueue.c:3322 process_scheduled_works kernel/workqueue.c:3405 [inline] worker_thread+0x5ef/0xe50 kernel/workqueue.c:3486 kthread+0x370/0x450 kernel/kthread.c:436 ret_from_fork+0x72b/0xd50 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 --- 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