From: kernel test robot <oliver.sang@intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
<linux-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [daveh-devel:old-ucode-platform] [x86/microcode] 19fb9a6d87: UBSAN:shift-out-of-bounds_in_arch/x86/kernel/cpu/match.c
Date: Thu, 20 Nov 2025 10:56:12 +0800 [thread overview]
Message-ID: <202511200314.3033cba4-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "UBSAN:shift-out-of-bounds_in_arch/x86/kernel/cpu/match.c" on:
commit: 19fb9a6d870e83926b240ba86a3e35870fa2e578 ("x86/microcode: Add platform mask to Intel microcode version list")
https://git.kernel.org/cgit/linux/kernel/git/daveh/devel.git old-ucode-platform
in testcase: lkvs
version: lkvs-x86_64-6d7ca2c-1_20251014
with following parameters:
test: cstate-client
config: x86_64-rhel-9.4-func
compiler: gcc-14
test machine: 22 threads 1 sockets Intel(R) Core(TM) Ultra 9 185H @ 4.5GHz (Meteor Lake) with 32G memory
(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/202511200314.3033cba4-lkp@intel.com
kern :warn : [ 0.000000] [ T0] ------------[ cut here ]------------
kern :err : [ 0.000000] [ T0] UBSAN: shift-out-of-bounds in arch/x86/kernel/cpu/match.c:80:9
kern :err : [ 0.000000] [ T0] shift exponent 128 is too large for 64-bit type 'long unsigned int'
kern :warn : [ 0.000000] [ T0] CPU: 0 UID: 0 PID: 0 Comm: swapper Not tainted 6.18.0-rc5-00007-g19fb9a6d870e #1 PREEMPT(undef)
kern :warn : [ 0.000000] [ T0] Call Trace:
kern :warn : [ 0.000000] [ T0] <TASK>
kern :warn : [ 0.000000] [ T0] ? dump_stack_lvl (lib/dump_stack.c:122)
kern :warn : [ 0.000000] [ T0] ? ubsan_epilogue (lib/ubsan.c:234 (discriminator 1))
kern :warn : [ 0.000000] [ T0] ? __ubsan_handle_shift_out_of_bounds.cold (lib/ubsan.c:494)
kern :warn : [ 0.000000] [ T0] ? __pfx_check_cpufeature_deps (arch/x86/kernel/cpu/cpuid-deps.c:172)
kern :warn : [ 0.000000] [ T0] ? x86_match_cpu.cold (arch/x86/kernel/cpu/match.c:80)
kern :warn : [ 0.000000] [ T0] ? cpu_set_bug_bits+0x18/0x1980
kern :warn : [ 0.000000] [ T0] ? early_identify_cpu+0x1d2/0x270
kern :warn : [ 0.000000] [ T0] ? setup_arch (arch/x86/kernel/setup.c:934)
kern :warn : [ 0.000000] [ T0] ? mutex_lock (arch/x86/include/asm/atomic64_64.h:101 (discriminator 5) include/linux/atomic/atomic-arch-fallback.h:4296 (discriminator 5) include/linux/atomic/atomic-long.h:1482 (discriminator 5) include/linux/atomic/atomic-instrumented.h:4458 (discriminator 5) kernel/locking/mutex.c:157 (discriminator 5) kernel/locking/mutex.c:273 (discriminator 5))
kern :warn : [ 0.000000] [ T0] ? __pfx_setup_arch (arch/x86/kernel/setup.c:881)
kern :warn : [ 0.000000] [ T0] ? _printk (kernel/printk/printk.c:2443)
kern :warn : [ 0.000000] [ T0] ? __pfx__printk (kernel/printk/printk.c:2443)
kern :warn : [ 0.000000] [ T0] ? cgroup_init_early (kernel/cgroup/cgroup.c:6327 (discriminator 3))
kern :warn : [ 0.000000] [ T0] ? start_kernel (init/main.c:934)
kern :warn : [ 0.000000] [ T0] ? x86_64_start_reservations (arch/x86/kernel/head64.c:310)
kern :warn : [ 0.000000] [ T0] ? x86_64_start_kernel (??:?)
kern :warn : [ 0.000000] [ T0] ? common_startup_64 (arch/x86/kernel/head_64.S:419)
kern :warn : [ 0.000000] [ T0] </TASK>
kern :warn : [ 0.000000] [ T0] ---[ end trace ]---
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251120/202511200314.3033cba4-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-20 2:56 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=202511200314.3033cba4-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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.