From: kernel test robot <oliver.sang@intel.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <linux-mm@kvack.org>,
"David Rientjes" <rientjes@google.com>,
Christoph Lameter <cl@linux.com>,
"Hyeonggon Yoo" <42.hyeyoo@gmail.com>,
Jay Patel <jaypatel@linux.ibm.com>,
"Roman Gushchin" <roman.gushchin@linux.dev>,
Pekka Enberg <penberg@kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>, <patches@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, Vlastimil Babka <vbabka@suse.cz>,
<oliver.sang@intel.com>
Subject: Re: [PATCH 4/4] mm/slub: refactor calculate_order() and calc_slab_order()
Date: Mon, 11 Sep 2023 13:56:52 +0800 [thread overview]
Message-ID: <202309111340.f59c3f22-oliver.sang@intel.com> (raw)
In-Reply-To: <20230908145302.30320-10-vbabka@suse.cz>
Hello,
kernel test robot noticed "UBSAN:shift-out-of-bounds_in_mm/slub.c" on:
commit: f04d441027621c16081803832a54f59272112cf5 ("[PATCH 4/4] mm/slub: refactor calculate_order() and calc_slab_order()")
url: https://github.com/intel-lab-lkp/linux/commits/Vlastimil-Babka/mm-slub-simplify-the-last-resort-slab-order-calculation/20230908-225506
base: git://git.kernel.org/cgit/linux/kernel/git/vbabka/slab.git for-next
patch link: https://lore.kernel.org/all/20230908145302.30320-10-vbabka@suse.cz/
patch subject: [PATCH 4/4] mm/slub: refactor calculate_order() and calc_slab_order()
in testcase: boot
compiler: clang-16
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+-------------------------------------------------+------------+------------+
| | a17847b835 | f04d441027 |
+-------------------------------------------------+------------+------------+
| UBSAN:shift-out-of-bounds_in_mm/slub.c | 0 | 12 |
+-------------------------------------------------+------------+------------+
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/202309111340.f59c3f22-oliver.sang@intel.com
[ 0.901457][ T0] UBSAN: shift-out-of-bounds in mm/slub.c:463:34
[ 0.902458][ T0] shift exponent 52 is too large for 32-bit type 'unsigned int'
[ 0.903477][ T0] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G T 6.5.0-rc1-00009-gf04d44102762 #1
[ 0.904450][ T0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 0.904450][ T0] Call Trace:
[ 0.904450][ T0] <TASK>
[ 0.904450][ T0] dump_stack_lvl (lib/dump_stack.c:107)
[ 0.904450][ T0] dump_stack (lib/dump_stack.c:114)
[ 0.904450][ T0] ubsan_epilogue (lib/ubsan.c:218)
[ 0.904450][ T0] __ubsan_handle_shift_out_of_bounds (lib/ubsan.c:?)
[ 0.904450][ T0] ? tdx_handle_virt_exception (arch/x86/include/asm/shared/tdx.h:60 arch/x86/coco/tdx/tdx.c:375 arch/x86/coco/tdx/tdx.c:430 arch/x86/coco/tdx/tdx.c:650 arch/x86/coco/tdx/tdx.c:666)
[ 0.904450][ T0] ? kmemleak_alloc (mm/kmemleak.c:977)
[ 0.904450][ T0] __kmem_cache_create (mm/slub.c:? mm/slub.c:4159 mm/slub.c:4473 mm/slub.c:4507 mm/slub.c:5104)
[ 0.904450][ T0] ? kmem_cache_alloc (mm/slub.c:3502)
[ 0.904450][ T0] kmem_cache_create_usercopy (mm/slab_common.c:236 mm/slab_common.c:340)
[ 0.904450][ T0] fork_init (kernel/fork.c:1048)
[ 0.904450][ T0] ? kmem_cache_create (mm/slab_common.c:395)
[ 0.904450][ T0] start_kernel (init/main.c:1046)
[ 0.904450][ T0] x86_64_start_reservations (??:?)
[ 0.904450][ T0] x86_64_start_kernel (arch/x86/kernel/head64.c:486)
[ 0.904450][ T0] secondary_startup_64_no_verify (arch/x86/kernel/head_64.S:441)
[ 0.904450][ T0] </TASK>
[ 0.904457][ T0] ================================================================================
[ 0.905560][ T0] LSM: initializing lsm=lockdown,capability,landlock,yama,safesetid,integrity
[ 0.906497][ T0] landlock: Up and running.
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230911/202309111340.f59c3f22-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-11 5:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 14:53 [PATCH 0/4] SLUB: calculate_order() cleanups Vlastimil Babka
2023-09-08 14:53 ` [PATCH 1/4] mm/slub: simplify the last resort slab order calculation Vlastimil Babka
2023-09-19 7:56 ` Feng Tang
2023-09-20 6:38 ` Vlastimil Babka
2023-09-20 7:09 ` Feng Tang
2023-09-08 14:53 ` [PATCH 2/4] mm/slub: remove min_objects loop from calculate_order() Vlastimil Babka
2023-09-08 14:53 ` [PATCH 3/4] mm/slub: attempt to find layouts up to 1/2 waste in calculate_order() Vlastimil Babka
2023-09-20 13:11 ` Feng Tang
2023-09-08 14:53 ` [PATCH 4/4] mm/slub: refactor calculate_order() and calc_slab_order() Vlastimil Babka
2023-09-11 5:56 ` kernel test robot [this message]
2023-09-15 13:36 ` Vlastimil Babka
2023-09-16 1:28 ` Baoquan He
2023-09-22 7:00 ` Vlastimil Babka
2023-09-22 7:29 ` Baoquan He
2023-09-20 13:36 ` Feng Tang
2023-09-22 6:55 ` Vlastimil Babka
2023-09-28 4:46 ` [PATCH 0/4] SLUB: calculate_order() cleanups Jay Patel
2023-10-02 12:38 ` Vlastimil Babka
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=202309111340.f59c3f22-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=42.hyeyoo@gmail.com \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jaypatel@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=patches@lists.linux.dev \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).