From: kernel test robot <oliver.sang@intel.com>
To: Kairui Song <kasong@tencent.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Matthew Wilcox" <willy@infradead.org>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linux-next:master] [lib/xarray] 5053ab0c89: WARNING:suspicious_RCU_usage
Date: Sat, 6 Apr 2024 11:25:42 +0800 [thread overview]
Message-ID: <202404061058.f2256e40-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "WARNING:suspicious_RCU_usage" on:
commit: 5053ab0c89ee4ba827db6a4453af277321cb1a2e ("lib/xarray: introduce a new helper xas_get_order")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 8568bb2ccc278f344e6ac44af6ed010a90aa88dc]
in testcase: boot
compiler: clang-17
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+---------------------------------------------------------------------+------------+------------+
| | cc93de5055 | 5053ab0c89 |
+---------------------------------------------------------------------+------------+------------+
| WARNING:suspicious_RCU_usage | 0 | 6 |
| include/linux/xarray.h:#suspicious_rcu_dereference_check()usage | 0 | 6 |
| include/linux/xarray.h:#suspicious_rcu_dereference_protected()usage | 0 | 6 |
+---------------------------------------------------------------------+------------+------------+
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/202404061058.f2256e40-lkp@intel.com
[ 242.400377][ T1] WARNING: suspicious RCU usage
[ 242.401381][ T1] 6.9.0-rc2-00150-g5053ab0c89ee #1 Tainted: G W N
[ 242.402989][ T1] -----------------------------
[ 242.404031][ T1] include/linux/xarray.h:1201 suspicious rcu_dereference_check() usage!
[ 242.405805][ T1]
[ 242.405805][ T1] other info that might help us debug this:
[ 242.405805][ T1]
[ 242.407877][ T1]
[ 242.407877][ T1] rcu_scheduler_active = 2, debug_locks = 1
[ 242.409774][ T1] no locks held by swapper/0/1.
[ 242.410827][ T1]
[ 242.410827][ T1] stack backtrace:
[ 242.412091][ T1] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W N 6.9.0-rc2-00150-g5053ab0c89ee #1
[ 242.413055][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 242.413055][ T1] Call Trace:
[ 242.413055][ T1] <TASK>
[ 242.413055][ T1] dump_stack_lvl (lib/dump_stack.c:116)
[ 242.413055][ T1] lockdep_rcu_suspicious (include/linux/context_tracking.h:122)
[ 242.413055][ T1] xas_start (include/linux/xarray.h:?)
[ 242.413055][ T1] xas_store (lib/xarray.c:237 lib/xarray.c:789)
[ 242.413055][ T1] ? do_raw_spin_unlock (arch/x86/include/asm/atomic.h:23)
[ 242.413055][ T1] ? xas_load (lib/xarray.c:237)
[ 242.413055][ T1] check_xas_get_order (lib/test_xarray.c:?)
[ 242.413055][ T1] xarray_checks (lib/test_xarray.c:2070)
[ 242.413055][ T1] do_one_initcall (init/main.c:1238)
[ 242.413055][ T1] ? __cfi_xarray_checks (lib/test_xarray.c:2054)
[ 242.413055][ T1] ? kasan_save_track (arch/x86/include/asm/current.h:49 mm/kasan/common.c:60 mm/kasan/common.c:69)
[ 242.413055][ T1] ? kasan_save_track (mm/kasan/common.c:48 mm/kasan/common.c:68)
[ 242.413055][ T1] ? __kasan_kmalloc (mm/kasan/common.c:391)
[ 242.413055][ T1] ? __kmalloc_noprof (include/linux/kasan.h:211 mm/slub.c:4186 mm/slub.c:4199)
[ 242.413055][ T1] ? do_initcalls (init/main.c:1310)
[ 242.432382][ T1] ? kernel_init_freeable (init/main.c:1552)
[ 242.432382][ T1] ? kernel_init (init/main.c:1439)
[ 242.432382][ T1] ? ret_from_fork (arch/x86/kernel/process.c:153)
[ 242.432382][ T1] ? ret_from_fork_asm (arch/x86/entry/entry_64.S:256)
[ 242.432382][ T1] ? parameq (kernel/params.c:81)
[ 242.432382][ T1] ? parameq (include/linux/fortify-string.h:250 kernel/params.c:99)
[ 242.432382][ T1] ? __cfi_ignore_unknown_bootoption (init/main.c:1285)
[ 242.432382][ T1] ? parse_args (kernel/params.c:?)
[ 242.432382][ T1] ? __kasan_kmalloc (mm/kasan/common.c:391)
[ 242.432382][ T1] do_initcall_level (init/main.c:1299)
[ 242.432382][ T1] do_initcalls (init/main.c:1313)
[ 242.432382][ T1] kernel_init_freeable (init/main.c:1552)
[ 242.432382][ T1] ? __cfi_kernel_init (init/main.c:1429)
[ 242.432382][ T1] kernel_init (init/main.c:1439)
[ 242.432382][ T1] ? __cfi_kernel_init (init/main.c:1429)
[ 242.432382][ T1] ret_from_fork (arch/x86/kernel/process.c:153)
[ 242.432382][ T1] ? __cfi_kernel_init (init/main.c:1429)
[ 242.432382][ T1] ret_from_fork_asm (arch/x86/entry/entry_64.S:256)
[ 242.432382][ T1] </TASK>
[ 242.451896][ T1]
[ 242.452554][ T1] =============================
[ 242.453552][ T1] WARNING: suspicious RCU usage
[ 242.454581][ T1] 6.9.0-rc2-00150-g5053ab0c89ee #1 Tainted: G W N
[ 242.456217][ T1] -----------------------------
[ 242.457261][ T1] include/linux/xarray.h:1217 suspicious rcu_dereference_check() usage!
[ 242.458920][ T1]
[ 242.458920][ T1] other info that might help us debug this:
[ 242.458920][ T1]
[ 242.461156][ T1]
[ 242.461156][ T1] rcu_scheduler_active = 2, debug_locks = 1
[ 242.462797][ T1] no locks held by swapper/0/1.
[ 242.463791][ T1]
[ 242.463791][ T1] stack backtrace:
[ 242.465126][ T1] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W N 6.9.0-rc2-00150-g5053ab0c89ee #1
[ 242.467116][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 242.468617][ T1] Call Trace:
[ 242.468617][ T1] <TASK>
[ 242.468617][ T1] dump_stack_lvl (lib/dump_stack.c:116)
[ 242.468617][ T1] lockdep_rcu_suspicious (include/linux/context_tracking.h:122)
[ 242.468617][ T1] xas_descend (include/linux/xarray.h:?)
[ 242.468617][ T1] xas_store (lib/xarray.c:244 lib/xarray.c:789)
[ 242.468617][ T1] ? do_raw_spin_unlock (arch/x86/include/asm/atomic.h:23)
[ 242.468617][ T1] ? xas_load (lib/xarray.c:244)
[ 242.468617][ T1] check_xas_get_order (lib/test_xarray.c:?)
[ 242.468617][ T1] xarray_checks (lib/test_xarray.c:2070)
[ 242.468617][ T1] do_one_initcall (init/main.c:1238)
[ 242.468617][ T1] ? __cfi_xarray_checks (lib/test_xarray.c:2054)
[ 242.468617][ T1] ? kasan_save_track (arch/x86/include/asm/current.h:49 mm/kasan/common.c:60 mm/kasan/common.c:69)
[ 242.468617][ T1] ? kasan_save_track (mm/kasan/common.c:48 mm/kasan/common.c:68)
[ 242.468617][ T1] ? __kasan_kmalloc (mm/kasan/common.c:391)
[ 242.468617][ T1] ? __kmalloc_noprof (include/linux/kasan.h:211 mm/slub.c:4186 mm/slub.c:4199)
[ 242.468617][ T1] ? do_initcalls (init/main.c:1310)
[ 242.468617][ T1] ? kernel_init_freeable (init/main.c:1552)
[ 242.468617][ T1] ? kernel_init (init/main.c:1439)
[ 242.468617][ T1] ? ret_from_fork (arch/x86/kernel/process.c:153)
[ 242.488373][ T1] ? ret_from_fork_asm (arch/x86/entry/entry_64.S:256)
[ 242.488373][ T1] ? parameq (kernel/params.c:81)
[ 242.488373][ T1] ? parameq (include/linux/fortify-string.h:250 kernel/params.c:99)
[ 242.488373][ T1] ? __cfi_ignore_unknown_bootoption (init/main.c:1285)
[ 242.488373][ T1] ? parse_args (kernel/params.c:?)
[ 242.488373][ T1] ? __kasan_kmalloc (mm/kasan/common.c:391)
[ 242.488373][ T1] do_initcall_level (init/main.c:1299)
[ 242.488373][ T1] do_initcalls (init/main.c:1313)
[ 242.488373][ T1] kernel_init_freeable (init/main.c:1552)
[ 242.488373][ T1] ? __cfi_kernel_init (init/main.c:1429)
[ 242.488373][ T1] kernel_init (init/main.c:1439)
[ 242.488373][ T1] ? __cfi_kernel_init (init/main.c:1429)
[ 242.488373][ T1] ret_from_fork (arch/x86/kernel/process.c:153)
[ 242.488373][ T1] ? __cfi_kernel_init (init/main.c:1429)
[ 242.488373][ T1] ret_from_fork_asm (arch/x86/entry/entry_64.S:256)
[ 242.488373][ T1] </TASK>
[ 242.505758][ T1]
[ 242.506807][ T1] =============================
[ 242.507842][ T1] WARNING: suspicious RCU usage
[ 242.508960][ T1] 6.9.0-rc2-00150-g5053ab0c89ee #1 Tainted: G W N
[ 242.510512][ T1] -----------------------------
[ 242.511564][ T1] include/linux/xarray.h:1226 suspicious rcu_dereference_protected() usage!
[ 242.513461][ T1]
[ 242.513461][ T1] other info that might help us debug this:
[ 242.513461][ T1]
[ 242.515528][ T1]
[ 242.515528][ T1] rcu_scheduler_active = 2, debug_locks = 1
[ 242.517330][ T1] no locks held by swapper/0/1.
[ 242.518364][ T1]
[ 242.518364][ T1] stack backtrace:
[ 242.519666][ T1] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W N 6.9.0-rc2-00150-g5053ab0c89ee #1
[ 242.520702][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 242.520702][ T1] Call Trace:
[ 242.520702][ T1] <TASK>
[ 242.520702][ T1] dump_stack_lvl (lib/dump_stack.c:116)
[ 242.520702][ T1] lockdep_rcu_suspicious (include/linux/context_tracking.h:122)
[ 242.520702][ T1] xas_store (include/linux/xarray.h:?)
[ 242.520702][ T1] check_xas_get_order (lib/test_xarray.c:?)
[ 242.520702][ T1] xarray_checks (lib/test_xarray.c:2070)
[ 242.520702][ T1] do_one_initcall (init/main.c:1238)
[ 242.520702][ T1] ? __cfi_xarray_checks (lib/test_xarray.c:2054)
[ 242.520702][ T1] ? kasan_save_track (arch/x86/include/asm/current.h:49 mm/kasan/common.c:60 mm/kasan/common.c:69)
[ 242.520702][ T1] ? kasan_save_track (mm/kasan/common.c:48 mm/kasan/common.c:68)
[ 242.520702][ T1] ? __kasan_kmalloc (mm/kasan/common.c:391)
[ 242.520702][ T1] ? __kmalloc_noprof (include/linux/kasan.h:211 mm/slub.c:4186 mm/slub.c:4199)
[ 242.520702][ T1] ? do_initcalls (init/main.c:1310)
[ 242.520702][ T1] ? kernel_init_freeable (init/main.c:1552)
[ 242.520702][ T1] ? kernel_init (init/main.c:1439)
[ 242.520702][ T1] ? ret_from_fork (arch/x86/kernel/process.c:153)
[ 242.520702][ T1] ? ret_from_fork_asm (arch/x86/entry/entry_64.S:256)
[ 242.520702][ T1] ? parameq (kernel/params.c:81)
[ 242.520702][ T1] ? parameq (include/linux/fortify-string.h:250 kernel/params.c:99)
[ 242.520702][ T1] ? __cfi_ignore_unknown_bootoption (init/main.c:1285)
[ 242.520702][ T1] ? parse_args (kernel/params.c:?)
[ 242.520702][ T1] ? __kasan_kmalloc (mm/kasan/common.c:391)
[ 242.520702][ T1] do_initcall_level (init/main.c:1299)
[ 242.520702][ T1] do_initcalls (init/main.c:1313)
[ 242.520702][ T1] kernel_init_freeable (init/main.c:1552)
[ 242.520702][ T1] ? __cfi_kernel_init (init/main.c:1429)
[ 242.520702][ T1] kernel_init (init/main.c:1439)
[ 242.520702][ T1] ? __cfi_kernel_init (init/main.c:1429)
[ 242.520702][ T1] ret_from_fork (arch/x86/kernel/process.c:153)
[ 242.520702][ T1] ? __cfi_kernel_init (init/main.c:1429)
[ 242.520702][ T1] ret_from_fork_asm (arch/x86/entry/entry_64.S:256)
[ 242.520702][ T1] </TASK>
[ 242.560253][ T1]
[ 242.560872][ T1] =============================
[ 242.561861][ T1] WARNING: suspicious RCU usage
[ 242.562854][ T1] 6.9.0-rc2-00150-g5053ab0c89ee #1 Tainted: G W N
[ 242.564501][ T1] -----------------------------
[ 242.565558][ T1] include/linux/xarray.h:1242 suspicious rcu_dereference_protected() usage!
[ 242.567300][ T1]
[ 242.567300][ T1] other info that might help us debug this:
[ 242.567300][ T1]
[ 242.569488][ T1]
[ 242.569488][ T1] rcu_scheduler_active = 2, debug_locks = 1
[ 242.571117][ T1] no locks held by swapper/0/1.
[ 242.572108][ T1]
[ 242.572108][ T1] stack backtrace:
[ 242.573465][ T1] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W N 6.9.0-rc2-00150-g5053ab0c89ee #1
[ 242.575431][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 242.576938][ T1] Call Trace:
[ 242.576938][ T1] <TASK>
[ 242.576938][ T1] dump_stack_lvl (lib/dump_stack.c:116)
[ 242.576938][ T1] lockdep_rcu_suspicious (include/linux/context_tracking.h:122)
[ 242.576938][ T1] xas_store (include/linux/xarray.h:?)
[ 242.576938][ T1] check_xas_get_order (lib/test_xarray.c:?)
[ 242.576938][ T1] xarray_checks (lib/test_xarray.c:2070)
[ 242.576938][ T1] do_one_initcall (init/main.c:1238)
[ 242.576938][ T1] ? __cfi_xarray_checks (lib/test_xarray.c:2054)
[ 242.576938][ T1] ? kasan_save_track (arch/x86/include/asm/current.h:49 mm/kasan/common.c:60 mm/kasan/common.c:69)
[ 242.576938][ T1] ? kasan_save_track (mm/kasan/common.c:48 mm/kasan/common.c:68)
[ 242.576938][ T1] ? __kasan_kmalloc (mm/kasan/common.c:391)
[ 242.576938][ T1] ? __kmalloc_noprof (include/linux/kasan.h:211 mm/slub.c:4186 mm/slub.c:4199)
[ 242.576938][ T1] ? do_initcalls (init/main.c:1310)
[ 242.576938][ T1] ? kernel_init_freeable (init/main.c:1552)
[ 242.576938][ T1] ? kernel_init (init/main.c:1439)
[ 242.576938][ T1] ? ret_from_fork (arch/x86/kernel/process.c:153)
[ 242.576938][ T1] ? ret_from_fork_asm (arch/x86/entry/entry_64.S:256)
[ 242.576938][ T1] ? parameq (kernel/params.c:81)
[ 242.576938][ T1] ? parameq (include/linux/fortify-string.h:250 kernel/params.c:99)
[ 242.576938][ T1] ? __cfi_ignore_unknown_bootoption (init/main.c:1285)
[ 242.576938][ T1] ? parse_args (kernel/params.c:?)
[ 242.576938][ T1] ? __kasan_kmalloc (mm/kasan/common.c:391)
[ 242.576938][ T1] do_initcall_level (init/main.c:1299)
[ 242.576938][ T1] do_initcalls (init/main.c:1313)
[ 242.576938][ T1] kernel_init_freeable (init/main.c:1552)
[ 242.576938][ T1] ? __cfi_kernel_init (init/main.c:1429)
[ 242.576938][ T1] kernel_init (init/main.c:1439)
[ 242.576938][ T1] ? __cfi_kernel_init (init/main.c:1429)
[ 242.576938][ T1] ret_from_fork (arch/x86/kernel/process.c:153)
[ 242.576938][ T1] ? __cfi_kernel_init (init/main.c:1429)
[ 242.576938][ T1] ret_from_fork_asm (arch/x86/entry/entry_64.S:256)
[ 242.576938][ T1] </TASK>
[ 260.158718][ T1] XArray: 158742827 of 158742827 tests passed
[ 260.160114][ T1]
[ 260.160114][ T1] TEST STARTING
[ 260.160114][ T1]
BUG: kernel hang in boot stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240406/202404061058.f2256e40-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-06 3:25 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=202404061058.f2256e40-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kasong@tencent.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=willy@infradead.org \
/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.