From: kernel test robot <oliver.sang@intel.com>
To: Chen Jinghuang <chenjinghuang2@huawei.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Chen Jinghuang <chenjinghuang2@huawei.com>,
<linux-kernel@vger.kernel.org>, <aubrey.li@linux.intel.com>,
<yu.c.chen@intel.com>, <mingo@redhat.com>, <peterz@infradead.org>,
<juri.lelli@redhat.com>, <vincent.guittot@linaro.org>,
<bsegall@google.com>, <dietmar.eggemann@arm.com>,
<rostedt@goodmis.org>, <mgorman@suse.de>, <vschneid@redhat.com>,
<kprateek.nayak@amd.com>, <chenl311@chinatelecom.cn>,
<steve.sistare@oracle.com>, <oliver.sang@intel.com>
Subject: Re: [RFC PATCH v5 4/9] sched/fair: Dynamically update cfs_overload_cpus
Date: Tue, 24 Mar 2026 21:56:56 +0800 [thread overview]
Message-ID: <202603242133.f66e336f-lkp@intel.com> (raw)
In-Reply-To: <20260320055920.2518389-5-chenjinghuang2@huawei.com>
Hello,
kernel test robot noticed "UBSAN:array-index-out-of-bounds_in_kernel/sched/sparsemask.h" on:
commit: 7c86475c501e5d551136d0c2c8702d7c61a6b73f ("[RFC PATCH v5 4/9] sched/fair: Dynamically update cfs_overload_cpus")
url: https://github.com/intel-lab-lkp/linux/commits/Chen-Jinghuang/sched-Provide-sparsemask-a-reduced-contention-bitmap/20260321-084706
base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git 42bddab0563fe67882b2722620a66dd98c8dbf33
patch link: https://lore.kernel.org/all/20260320055920.2518389-5-chenjinghuang2@huawei.com/
patch subject: [RFC PATCH v5 4/9] sched/fair: Dynamically update cfs_overload_cpus
in testcase: boot
config: x86_64-randconfig-016-20260323
compiler: clang-20
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/202603242133.f66e336f-lkp@intel.com
[ 3.884372][ T1] ------------[ cut here ]------------
[ 3.884372][ T1] UBSAN: array-index-out-of-bounds in kernel/sched/sparsemask.h:181:32
[ 3.884372][ T1] index 0 is out of range for type 'struct sparsemask_chunk[0]'
[ 3.884372][ T1] CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.0.0-rc4-00274-g7c86475c501e #1 PREEMPT 3f169c7b099bc50b6180dc864130cea2b43f07ba
[ 3.884372][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 3.884372][ T1] Call Trace:
[ 3.884372][ T1] <TASK>
[ 3.884372][ T1] __dump_stack (lib/dump_stack.c:95)
[ 3.884372][ T1] dump_stack_lvl (lib/dump_stack.c:123 (discriminator 1))
[ 3.884372][ T1] dump_stack (lib/dump_stack.c:130)
[ 3.884372][ T1] ubsan_epilogue (lib/ubsan.c:234 (discriminator 2))
[ 3.884372][ T1] __ubsan_handle_out_of_bounds (lib/ubsan.c:?)
[ 3.884372][ T1] ? overload_set (include/linux/rcupdate.h:312 (discriminator 1) include/linux/rcupdate.h:850 (discriminator 1) kernel/sched/fair.c:5164 (discriminator 1))
[ 3.884372][ T1] overload_set (kernel/sched/sparsemask.h:181 (discriminator 4) kernel/sched/fair.c:5167 (discriminator 4))
[ 3.884372][ T1] ? overload_set (include/linux/rcupdate.h:312 (discriminator 1) include/linux/rcupdate.h:850 (discriminator 1) kernel/sched/fair.c:5164 (discriminator 1))
[ 3.884372][ T1] enqueue_task_fair (kernel/sched/fair.c:401 kernel/sched/fair.c:7092)
[ 3.884372][ T1] enqueue_task (kernel/sched/core.c:2111)
[ 3.884372][ T1] ttwu_do_activate (kernel/sched/core.c:2149 (discriminator 4) kernel/sched/core.c:3667 (discriminator 4))
[ 3.884372][ T1] try_to_wake_up (kernel/sched/sched.h:1883 kernel/sched/sched.h:1969 kernel/sched/core.c:3919 kernel/sched/core.c:4242)
[ 3.884372][ T1] wake_up_process (kernel/sched/core.c:4374)
[ 3.884372][ T1] __kthread_create_on_node (kernel/kthread.c:?)
[ 3.884372][ T1] kthread_create_on_node (kernel/kthread.c:562)
[ 3.884372][ T1] rcu_spawn_tasks_kthread_generic (kernel/rcu/tasks.h:682 (discriminator 512))
[ 3.884372][ T1] rcu_init_tasks_generic (kernel/rcu/tasks.h:1587)
[ 3.884372][ T1] do_one_initcall (init/main.c:1382)
[ 3.884372][ T1] ? stack_depot_save_flags (lib/stackdepot.c:?)
[ 3.884372][ T1] ? tasks_cblist_init_generic (kernel/rcu/tasks.h:1577)
[ 3.884372][ T1] ? kasan_save_track (arch/x86/include/asm/current.h:25 (discriminator 3) mm/kasan/common.c:70 (discriminator 3) mm/kasan/common.c:79 (discriminator 3))
[ 3.884372][ T1] ? kasan_save_track (mm/kasan/common.c:58 mm/kasan/common.c:78)
[ 3.884372][ T1] ? kasan_save_alloc_info (mm/kasan/generic.c:571 (discriminator 1))
[ 3.884372][ T1] ? __kasan_kmalloc (mm/kasan/common.c:419)
[ 3.884372][ T1] ? __kmalloc_noprof (mm/slub.c:5261 mm/slub.c:5272)
[ 3.884372][ T1] ? do_initcalls (init/main.c:1454)
[ 3.884372][ T1] ? do_basic_setup (init/main.c:1480)
[ 3.884372][ T1] ? kernel_init_freeable (init/main.c:1694)
[ 3.884372][ T1] ? kernel_init (init/main.c:1584)
[ 3.884372][ T1] ? ret_from_fork (arch/x86/kernel/process.c:164)
[ 3.884372][ T1] ? ret_from_fork_asm (arch/x86/entry/entry_64.S:258)
[ 3.884372][ T1] ? _raw_spin_unlock_irqrestore (include/linux/spinlock_api_smp.h:179 (discriminator 1) kernel/locking/spinlock.c:194 (discriminator 1))
[ 3.884372][ T1] ? stack_depot_save_flags (lib/stackdepot.c:?)
[ 3.884372][ T1] ? stack_depot_save (lib/stackdepot.c:747)
[ 3.884372][ T1] ? set_track_prepare (mm/slub.c:1036)
[ 3.884372][ T1] ? do_initcalls (init/main.c:1454)
[ 3.884372][ T1] ? do_basic_setup (init/main.c:1480)
[ 3.884372][ T1] ? kernel_init_freeable (init/main.c:1694)
[ 3.884372][ T1] ? kernel_init (init/main.c:1584)
[ 3.884372][ T1] ? ret_from_fork (arch/x86/kernel/process.c:164)
[ 3.884372][ T1] ? ret_from_fork_asm (arch/x86/entry/entry_64.S:258)
[ 3.884372][ T1] ? next_arg (lib/cmdline.c:273)
[ 3.884372][ T1] ? parameq (kernel/params.c:90 (discriminator 1) kernel/params.c:99 (discriminator 1))
[ 3.884372][ T1] ? parse_args (kernel/params.c:153 kernel/params.c:186)
[ 3.884372][ T1] do_initcall_level (init/main.c:1443 (discriminator 6))
[ 3.884372][ T1] do_initcalls (init/main.c:1457 (discriminator 2))
[ 3.884372][ T1] ? kernel_init (init/main.c:1584)
[ 3.884372][ T1] do_basic_setup (init/main.c:1480)
[ 3.884372][ T1] kernel_init_freeable (init/main.c:1694)
[ 3.884372][ T1] ? rest_init (init/main.c:1574)
[ 3.884372][ T1] kernel_init (init/main.c:1584)
[ 3.884372][ T1] ? rest_init (init/main.c:1574)
[ 3.884372][ T1] ret_from_fork (arch/x86/kernel/process.c:164)
[ 3.884372][ T1] ? rest_init (init/main.c:1574)
[ 3.884372][ T1] ret_from_fork_asm (arch/x86/entry/entry_64.S:258)
[ 3.884372][ T1] </TASK>
[ 3.884372][ T1] ---[ end trace ]---
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260324/202603242133.f66e336f-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2026-03-24 13:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260320055920.2518389-5-chenjinghuang2@huawei.com>]
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=202603242133.f66e336f-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=bsegall@google.com \
--cc=chenjinghuang2@huawei.com \
--cc=chenl311@chinatelecom.cn \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=oe-lkp@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=steve.sistare@oracle.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yu.c.chen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox