From: kernel test robot <oliver.sang@intel.com>
To: Jann Horn <jannh@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Andrey Konovalov" <andreyknvl@gmail.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Christoph Lameter <cl@linux.com>,
David Rientjes <rientjes@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Marco Elver <elver@google.com>,
"Pekka Enberg" <penberg@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
<kasan-dev@googlegroups.com>, <oliver.sang@intel.com>
Subject: [linux-next:master] [slub] d543c8fb9c: BUG_filp(Not_tainted):Bulk_free_expected#objects_but_found
Date: Wed, 31 Jul 2024 13:27:25 +0800 [thread overview]
Message-ID: <202407311019.5ea52390-lkp@intel.com> (raw)
hi, Jann Horn,
we reported "WARNING:possible_circular_locking_dependency_detected"
issue upon v3 of this patch in
https://lore.kernel.org/all/202407291014.2ead1e72-oliver.sang@intel.com/
several days ago.
at that time, you said that real issue should be something like
"BUG filp (Not tainted): Bulk free expected 1 objects but found 2"
and you will send a fix.
now we noticed this patch in in linux-next/master, but not sure the version.
we found there are still similar issues so just send report to you FYI.
Hello,
kernel test robot noticed "BUG_filp(Not_tainted):Bulk_free_expected#objects_but_found" on:
commit: d543c8fb9c4caa95cd2799b9d3b6f6354140f4f4 ("slub: introduce CONFIG_SLUB_RCU_DEBUG")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master cd19ac2f903276b820f5d0d89de0c896c27036ed]
in testcase: rcutorture
version:
with following parameters:
runtime: 300s
test: cpuhotplug
torture_type: srcud
compiler: gcc-13
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(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/202407311019.5ea52390-lkp@intel.com
[ 243.911590][ T0] masked ExtINT on CPU#1
[ 244.087218][ T9] smpboot: CPU 1 is now offline
[ 244.154988][ T435] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 244.155553][ T0] masked ExtINT on CPU#1
[ 244.226610][ C1] =============================================================================
[ 244.227574][ C1] BUG filp (Not tainted): Bulk free expected 1 objects but found 2
[ 244.227574][ C1]
[ 244.228097][ C1] -----------------------------------------------------------------------------
[ 244.228097][ C1]
[ 244.228665][ C1] Slab 0xffffea0005dac500 objects=23 used=23 fp=0x0000000000000000 flags=0x8000000000000040(head|zone=2)
[ 244.229241][ C1] CPU: 1 UID: 0 PID: 22 Comm: cpuhp/1 Not tainted 6.10.0-12959-gd543c8fb9c4c #1
[ 244.229725][ C1] Call Trace:
[ 244.229909][ C1] <IRQ>
[ 244.230069][ C1] dump_stack_lvl (kbuild/src/consumer/lib/dump_stack.c:122)
[ 244.230337][ C1] slab_err (kbuild/src/consumer/mm/slub.c:1149)
[ 244.230606][ C1] ? check_object (kbuild/src/consumer/mm/slub.c:1293 kbuild/src/consumer/mm/slub.c:1391)
[ 244.230925][ C1] free_debug_processing (kbuild/src/consumer/mm/slub.c:3378)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240731/202407311019.5ea52390-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-07-31 5:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 5:27 kernel test robot [this message]
2024-07-31 11:50 ` [linux-next:master] [slub] d543c8fb9c: BUG_filp(Not_tainted):Bulk_free_expected#objects_but_found Jann Horn
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=202407311019.5ea52390-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jannh@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=ryabinin.a.a@gmail.com \
--cc=vincenzo.frascino@arm.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.