From: syzbot <syzbot+a308ee836af04d1d6fa6@syzkaller.appspotmail.com>
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
Subject: [syzbot] [mm?] WARNING in alloc_vmap_area
Date: Fri, 31 Jul 2026 17:36:41 -0700 [thread overview]
Message-ID: <6a6d3f99.13bfb6d0.1ecdd5.0255.GAE@google.com> (raw)
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:
<TASK>
__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
</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 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
reply other threads:[~2026-08-01 0:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6a6d3f99.13bfb6d0.1ecdd5.0255.GAE@google.com \
--to=syzbot+a308ee836af04d1d6fa6@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=bsegall@google.com \
--cc=david@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kees@kernel.org \
--cc=kprateek.nayak@amd.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.