From: kernel test robot <oliver.sang@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Gregory Price <gourry@gourry.net>, <oliver.sang@intel.com>
Subject: [gourryinverse:scratch/gourry/managed_nodes/rfc5] [mm/page_alloc] 78a7080812: UBSAN:array-index-out-of-bounds_in_linux/gfp.h
Date: Fri, 17 Jul 2026 10:06:11 +0800 [thread overview]
Message-ID: <202607170545.4e054b0-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "UBSAN:array-index-out-of-bounds_in_linux/gfp.h" on:
commit: 78a7080812fd60e3aca2770f42185c60fb9adc4c ("mm/page_alloc: node-strict private zonelist (ZONELIST_PRIVATE_NOFALLBACK)")
https://github.com/gourryinverse/linux scratch/gourry/managed_nodes/rfc5
in testcase: boot
config: x86_64-randconfig-r071-20260714
compiler: gcc-14
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202607170545.4e054b0-lkp@intel.com
[ 3.751402][ T0] ------------[ cut here ]------------
[ 3.752820][ T0] UBSAN: array-index-out-of-bounds in linux/gfp.h:236:40
[ 3.755156][ T0] index -33686020 is out of range for type 'zonelist [4]'
[ 3.757047][ T0] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 7.2.0-rc2-00020-g78a7080812fd #1 PREEMPT(full) 782b3f07ed27af074729c4232601262326f9252f
[ 3.757054][ T0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 3.757060][ T0] Call Trace:
[ 3.757063][ T0] <TASK>
[ 3.757076][ T0] dump_stack_lvl (dump_stack.c:94 dump_stack.c:120)
[ 3.757087][ T0] ubsan_epilogue (ubsan.c:233)
[ 3.757093][ T0] __ubsan_handle_out_of_bounds (ubsan.c:455)
[ 3.757109][ T0] prepare_alloc_pages+0xd6/0x330
[ 3.757119][ T0] alloc_pages_bulk_noprof (page_alloc.c:5145)
[ 3.757129][ T0] ? __alloc_pages_noprof (page_alloc.c:5358)
[ 3.757134][ T0] ? policy_nodemask (mempolicy.c:2311)
[ 3.757149][ T0] __kasan_populate_vmalloc_do (kasan/shadow.c:345 (discriminator 3) kasan/shadow.c:370 (discriminator 3))
[ 3.757158][ T0] alloc_vmap_area (linux/kasan.h:580 vmalloc.c:2123)
[ 3.757170][ T0] ? reclaim_and_purge_vmap_areas (vmalloc.c:2425)
[ 3.757175][ T0] ? local_clock (sched/clock.c:321)
[ 3.757181][ T0] ? kasan_set_track (kasan/common.c:65)
[ 3.757190][ T0] ? __kmalloc_cache_node_noprof (linux/kasan.h:263 slub.c:5534)
[ 3.757197][ T0] ? __get_vm_area_node (linux/slab.h:1174 vmalloc.c:3215)
[ 3.757205][ T0] __get_vm_area_node (vmalloc.c:3226)
[ 3.757230][ T0] ? irq_init_percpu_irqstack (x86/kernel/irq_64.c:49 x86/kernel/irq_64.c:76)
[ 3.757236][ T0] get_vm_area_caller (vmalloc.c:3277)
[ 3.757241][ T0] ? irq_init_percpu_irqstack (x86/kernel/irq_64.c:49 x86/kernel/irq_64.c:76)
[ 3.757246][ T0] vmap (vmalloc.c:3560 (discriminator 1))
[ 3.757252][ T0] ? vunmap (vmalloc.c:3519)
[ 3.757255][ T0] ? __lock_release+0x5a/0x150
[ 3.757261][ T0] ? rcu_read_unlock (linux/rcupdate.h:310 (discriminator 1) linux/rcupdate.h:871 (discriminator 1))
[ 3.757274][ T0] irq_init_percpu_irqstack (x86/kernel/irq_64.c:49 x86/kernel/irq_64.c:76)
[ 3.757295][ T0] ? fred_sysvec_thermal (??:?)
[ 3.757302][ T0] ? mp_check_pin_attr (x86/kernel/apic/io_apic.c:880)
[ 3.757309][ T0] ? alloc_ioapic_saved_registers (x86/kernel/apic/io_apic.c:226 (discriminator 3) x86/kernel/apic/io_apic.c:218 (discriminator 3))
[ 3.757318][ T0] init_IRQ (x86/kernel/irqinit.c:90 (discriminator 10))
[ 3.757329][ T0] start_kernel (main.c:1079)
[ 3.757333][ T0] x86_64_start_reservations (x86/kernel/head64.c:310)
[ 3.757338][ T0] x86_64_start_kernel (x86/kernel/head64.c:291)
[ 3.757344][ T0] common_startup_64 (x86/kernel/head_64.S:418)
[ 3.757358][ T0] </TASK>
[ 3.757360][ T0] ---[ end trace ]---
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260717/202607170545.4e054b0-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-17 2:06 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=202607170545.4e054b0-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=gourry@gourry.net \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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.