From: syzbot <syzbot+61c997e6be1d9bb300ba@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 va_alloc
Date: Fri, 31 Jul 2026 17:24:29 -0700 [thread overview]
Message-ID: <6a6d3cbd.6ce73036.24301b.000e.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=16efd632580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c05be6c9b0d36cb9
dashboard link: https://syzkaller.appspot.com/bug?extid=61c997e6be1d9bb300ba
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 (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-11028ab6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/511647651d7f/vmlinux-11028ab6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1c76180d0109/bzImage-11028ab6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+61c997e6be1d9bb300ba@syzkaller.appspotmail.com
FAULT_INJECTION: forcing a failure.
name failslab, interval 1, probability 1, space 0, times 977
CPU: 0 UID: 0 PID: 5320 Comm: syz.0.0 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_lvl+0xe8/0x150 lib/dump_stack.c:120
fail_dump lib/fault-inject.c:73 [inline]
should_fail_ex+0x40c/0x560 lib/fault-inject.c:174
should_failslab+0xa8/0x100 mm/failslab.c:46
slab_pre_alloc_hook mm/slub.c:4539 [inline]
slab_alloc_node mm/slub.c:4897 [inline]
kmem_cache_alloc_node_noprof+0xb3/0x610 mm/slub.c:4989
preload_this_cpu_lock+0x49/0xc0 mm/vmalloc.c:1902
alloc_vmap_area+0x3c3/0x1420 mm/vmalloc.c:2072
__get_vm_area_node+0x1f2/0x300 mm/vmalloc.c:3226
__vmalloc_node_range_noprof+0x358/0x1730 mm/vmalloc.c:4042
__vmalloc_node_noprof+0xc2/0x100 mm/vmalloc.c:4143
alloc_thread_stack_node kernel/fork.c:359 [inline]
dup_task_struct+0x2a0/0x8e0 kernel/fork.c:929
copy_process+0x820/0x4390 kernel/fork.c:2115
kernel_clone+0x2d7/0x940 kernel/fork.c:2748
__do_sys_clone3 kernel/fork.c:3050 [inline]
__se_sys_clone3+0x33c/0x360 kernel/fork.c:3029
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9d8f39ed89
Code: 90 b8 01 00 00 00 b9 01 00 00 00 eb ec 0f 1f 40 00 b8 ea ff ff ff 48 85 ff 74 28 48 85 d2 74 23 49 89 c8 b8 b3 01 00 00 0f 05 <48> 85 c0 7c 14 74 01 c3 31 ed 4c 89 c7 ff d2 48 89 c7 b8 3c 00 00
RSP: 002b:00007fffcf746358 EFLAGS: 00000202 ORIG_RAX: 00000000000001b3
RAX: ffffffffffffffda RBX: 00007f9d8f35a320 RCX: 00007f9d8f39ed89
RDX: 00007f9d8f35a320 RSI: 0000000000000058 RDI: 00007fffcf7463b0
RBP: 00007f9d902776c0 R08: 00007f9d902776c0 R09: 00007fffcf746497
R10: 0000000000000008 R11: 0000000000000202 R12: ffffffffffffffe8
R13: 000000000000006e R14: 00007fffcf7463b0 R15: 00007fffcf746498
</TASK>
------------[ cut here ]------------
ret
WARNING: mm/vmalloc.c:1820 at va_alloc+0xeb/0xec0 mm/vmalloc.c:1820, CPU#0: syz.0.0/5320
Modules linked in:
CPU: 0 UID: 0 PID: 5320 Comm: syz.0.0 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
RIP: 0010:va_alloc+0xeb/0xec0 mm/vmalloc.c:1820
Code: 08 4c 89 ef e8 16 98 10 00 4d 8b 7d 00 48 89 df 4c 89 fe e8 97 69 a1 ff 4c 39 fb 76 27 e8 2d 67 a1 ff 49 c7 c6 ea ff ff ff 90 <0f> 0b 90 4c 89 f0 48 83 c4 58 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc
RSP: 0018:ffffc9000f5e74b0 EFLAGS: 00010293
RAX: ffffffff8225caea RBX: ffffc9000f679000 RCX: ffff88801fae2540
RDX: 0000000000000000 RSI: ffffffff8c4bed60 RDI: ffffffff8c4bed20
RBP: ffff88803f07ef08 R08: 00000000ffffffff R09: 1ffffffff1d94962
R10: dffffc0000000000 R11: fffffbfff1d94963 R12: 1ffff11007e0fde1
R13: ffffc9000f670000 R14: fffffffffffffff4 R15: 0000000000000000
FS: 000055557c363540(0000) GS:ffff88808c543000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9d90277d58 CR3: 0000000012236000 CR4: 0000000000352ef0
Call Trace:
<TASK>
__alloc_vmap_area mm/vmalloc.c:1855 [inline]
alloc_vmap_area+0x907/0x1420 mm/vmalloc.c:2073
__get_vm_area_node+0x1f2/0x300 mm/vmalloc.c:3226
__vmalloc_node_range_noprof+0x358/0x1730 mm/vmalloc.c:4042
__vmalloc_node_noprof+0xc2/0x100 mm/vmalloc.c:4143
alloc_thread_stack_node kernel/fork.c:359 [inline]
dup_task_struct+0x2a0/0x8e0 kernel/fork.c:929
copy_process+0x820/0x4390 kernel/fork.c:2115
kernel_clone+0x2d7/0x940 kernel/fork.c:2748
__do_sys_clone3 kernel/fork.c:3050 [inline]
__se_sys_clone3+0x33c/0x360 kernel/fork.c:3029
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9d8f39ed89
Code: 90 b8 01 00 00 00 b9 01 00 00 00 eb ec 0f 1f 40 00 b8 ea ff ff ff 48 85 ff 74 28 48 85 d2 74 23 49 89 c8 b8 b3 01 00 00 0f 05 <48> 85 c0 7c 14 74 01 c3 31 ed 4c 89 c7 ff d2 48 89 c7 b8 3c 00 00
RSP: 002b:00007fffcf746358 EFLAGS: 00000202 ORIG_RAX: 00000000000001b3
RAX: ffffffffffffffda RBX: 00007f9d8f35a320 RCX: 00007f9d8f39ed89
RDX: 00007f9d8f35a320 RSI: 0000000000000058 RDI: 00007fffcf7463b0
RBP: 00007f9d902776c0 R08: 00007f9d902776c0 R09: 00007fffcf746497
R10: 0000000000000008 R11: 0000000000000202 R12: ffffffffffffffe8
R13: 000000000000006e R14: 00007fffcf7463b0 R15: 00007fffcf746498
</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:24 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=6a6d3cbd.6ce73036.24301b.000e.GAE@google.com \
--to=syzbot+61c997e6be1d9bb300ba@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.