From: kernel test robot <oliver.sang@intel.com>
To: <jasperwang@tencent.com>, <kaixuxia@tencent.com>,
<frankjpliu@tencent.com>, <kasong@tencent.com>,
<sagazchen@tencent.com>, <kernelxing@tencent.com>,
<aurelianliu@tencent.com>, <jason.zeng@intel.com>,
<wu.zheng@intel.com>, <yingbao.jia@intel.com>,
<pei.p.jia@intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <oliver.sang@intel.com>
Subject: [opencloudos:linux-5.4/lts/5.4.119-20.0009.spr] [intel_idle] 42c771b6dd: WARNING:suspicious_RCU_usage
Date: Tue, 30 Apr 2024 17:02:45 +0800 [thread overview]
Message-ID: <202404301635.1294804e-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "WARNING:suspicious_RCU_usage" on:
commit: 42c771b6dd50c65af13b8a3f51a6e8689f6af3b5 ("intel_idle: add Emerald Rapids Xeon support")
https://gitee.com/OpenCloudOS/OpenCloudOS-Kernel.git linux-5.4/lts/5.4.119-20.0009.spr
in testcase: kernel-selftests
version: kernel-selftests-x86_64-c7864053-1_20240419
with following parameters:
group: netfilter
test: nft_conntrack_helper.sh
compiler: gcc-12
test machine: 256 threads 4 sockets INTEL(R) XEON(R) PLATINUM 8592+ (Emerald Rapids) with 256G 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/202404301635.1294804e-lkp@intel.com
kern :warn : [ 183.635146] WARNING: suspicious RCU usage
kern :warn : [ 183.640454] 5.4.119-20-g42c771b6dd50 #1 Not tainted
kern :warn : [ 183.646737] -----------------------------
kern :warn : [ 183.652044] include/trace/events/tlb.h:38 suspicious rcu_dereference_check() usage!
kern :warn : [ 183.661454]
other info that might help us debug this:
kern :warn : [ 183.672818]
RCU used illegally from idle CPU!
rcu_scheduler_active = 2, debug_locks = 1
kern :warn : [ 183.687404] RCU used illegally from extended quiescent state!
kern :warn : [ 183.694664] no locks held by swapper/202/0.
kern :warn : [ 183.700164]
stack backtrace:
kern :warn : [ 183.706647] CPU: 202 PID: 0 Comm: swapper/202 Not tainted 5.4.119-20-g42c771b6dd50 #1
kern :warn : [ 183.716252] Call Trace:
kern :warn : [ 183.719801] dump_stack (lib/dump_stack.c:120)
kern :warn : [ 183.724331] lockdep_rcu_suspicious (kernel/locking/lockdep.c:5449)
kern :warn : [ 183.730229] trace_tlb_flush (include/trace/events/tlb.h:38 include/trace/events/tlb.h:38)
kern :warn : [ 183.735440] switch_mm_irqs_off (arch/x86/mm/tlb.c:430)
kern :warn : [ 183.740944] ? trace_hardirqs_off (kernel/trace/trace_preemptirq.c:46)
kern :warn : [ 183.746549] leave_mm (arch/x86/mm/tlb.c:161 arch/x86/mm/tlb.c:150)
kern :warn : [ 183.750883] cpuidle_enter_state (drivers/cpuidle/cpuidle.c:230)
kern :warn : [ 183.756485] ? lockdep_hardirqs_on (kernel/locking/lockdep.c:3395 kernel/locking/lockdep.c:3440)
kern :warn : [ 183.762282] ? rcu_idle_exit (arch/x86/include/asm/irqflags.h:41 (discriminator 2) arch/x86/include/asm/irqflags.h:84 (discriminator 2) kernel/rcu/tree.c:775 (discriminator 2))
kern :warn : [ 183.767490] ? trace_hardirqs_on (kernel/trace/trace_preemptirq.c:32 (discriminator 38))
kern :warn : [ 183.772997] cpuidle_enter (include/linux/compiler.h:293 drivers/cpuidle/cpuidle.c:352)
kern :warn : [ 183.777822] cpuidle_idle_call (kernel/sched/idle.c:117 kernel/sched/idle.c:207)
kern :warn : [ 183.783230] ? arch_cpu_idle_exit+0x40/0x40
kern :warn : [ 183.788732] ? __kasan_check_read (mm/kasan/common.c:93)
kern :warn : [ 183.794237] do_idle (kernel/sched/idle.c:270)
kern :warn : [ 183.798571] cpu_startup_entry (kernel/sched/idle.c:361 (discriminator 1))
kern :warn : [ 183.803783] start_secondary (arch/x86/kernel/smpboot.c:272)
kern :warn : [ 183.808995] ? set_cpu_sibling_map (arch/x86/kernel/smpboot.c:212)
kern :warn : [ 183.814992] secondary_startup_64 (arch/x86/kernel/head_64.S:241)
kern :warn : [ 183.820521] =============================
kern :warn : [ 183.820521] WARNING: suspicious RCU usage
kern :warn : [ 183.820521] 5.4.119-20-g42c771b6dd50 #1 Not tainted
kern :warn : [ 183.820522] -----------------------------
kern :warn : [ 183.820523] include/linux/rcupdate.h:620 rcu_read_lock() used illegally while idle!
kern :warn : [ 183.820523] other info that might help us debug this:
kern :warn : [ 183.820525] RCU used illegally from idle CPU!
kern :warn : [ 183.820525] rcu_scheduler_active = 2, debug_locks = 1
kern :warn : [ 183.820526] RCU used illegally from extended quiescent state!
kern :warn : [ 183.820526] 4 locks held by swapper/202/0:
kern :warn : [ 183.820526] #0: ffffffff85632b80 (console_lock){+.+.}, at: vprintk_emit (kernel/printk/printk.c:2023)
kern :warn : [ 183.820529] #1: ffffffff856326c0 (console_owner){-...}, at: console_unlock (kernel/printk/printk.c:2493)
kern :warn : [ 183.820531] #2: ffffffff85c97ff8 (printing_lock){....}, at: vt_console_print (drivers/tty/vt/vt.c:2966)
kern :warn : [ 183.820533] #3: ffffffff85656420 (rcu_read_lock){....}, at: __atomic_notifier_call_chain (kernel/notifier.c:185)
kern :warn : [ 183.820536] stack backtrace:
kern :warn : [ 183.820536] CPU: 202 PID: 0 Comm: swapper/202 Not tainted 5.4.119-20-g42c771b6dd50 #1
kern :warn : [ 183.820537] Call Trace:
kern :warn : [ 183.820537] dump_stack (lib/dump_stack.c:120)
kern :warn : [ 183.820538] lockdep_rcu_suspicious (kernel/locking/lockdep.c:5449)
kern :warn : [ 183.820538] __atomic_notifier_call_chain (include/linux/rcupdate.h:620 kernel/notifier.c:188)
kern :warn : [ 183.820538] atomic_notifier_call_chain (kernel/notifier.c:200)
kern :warn : [ 183.820539] vt_console_print (drivers/tty/vt/vt.c:3013)
kern :warn : [ 183.820539] ? serial8250_config_port (drivers/tty/serial/8250/8250_port.c:3166)
kern :warn : [ 183.820540] ? unblank_screen (drivers/tty/vt/vt.c:2955)
kern :warn : [ 183.820540] call_console_drivers+0x16c/0x2e0
kern :warn : [ 183.820541] console_unlock (kernel/printk/printk.c:2505)
kern :warn : [ 183.820541] ? console_unlock (kernel/printk/printk.c:2493)
kern :warn : [ 183.820542] ? __down_trylock_console_sem (kernel/printk/printk.c:243)
kern :warn : [ 183.820542] ? vprintk_emit (kernel/printk/printk.c:2023)
kern :warn : [ 183.820542] vprintk_emit (kernel/printk/printk.c:2024)
kern :warn : [ 183.820543] vprintk_default (kernel/printk/printk.c:2054)
kern :warn : [ 183.820543] vprintk_func (kernel/printk/printk_safe.c:394)
kern :warn : [ 183.820544] ? trace_hardirqs_off (kernel/trace/trace_preemptirq.c:46)
kern :warn : [ 183.820544] printk (kernel/printk/printk.c:2079)
kern :warn : [ 183.820545] ? log_store.cold (kernel/printk/printk.c:2079)
kern :warn : [ 183.820545] ? tick_nohz_next_event (kernel/time/tick-sched.c:717)
kern :warn : [ 183.820546] ? tick_nohz_restart (kernel/time/tick-sched.c:661)
kern :warn : [ 183.820546] ? trace_hardirqs_on_thunk (arch/x86/entry/thunk_64.S:41)
kern :warn : [ 183.820546] ? trace_hardirqs_on_caller (kernel/trace/trace_preemptirq.c:60 (discriminator 38))
kern :warn : [ 183.820547] ? __kasan_check_read (mm/kasan/common.c:93)
kern :warn : [ 183.820547] ? rcu_is_watching (include/linux/compiler.h:266 arch/x86/include/asm/atomic.h:31 include/asm-generic/atomic-instrumented.h:27 kernel/rcu/tree.c:301 kernel/rcu/tree.c:908)
kern :warn : [ 183.820548] lockdep_rcu_suspicious (kernel/locking/lockdep.c:5411)
kern :warn : [ 183.820548] trace_tlb_flush (include/trace/events/tlb.h:38 include/trace/events/tlb.h:38)
kern :warn : [ 183.820549] switch_mm_irqs_off (arch/x86/mm/tlb.c:430)
kern :warn : [ 183.820549] ? trace_hardirqs_off (kernel/trace/trace_preemptirq.c:46)
kern :warn : [ 183.820549] leave_mm (arch/x86/mm/tlb.c:161 arch/x86/mm/tlb.c:150)
kern :warn : [ 183.820550] cpuidle_enter_state (drivers/cpuidle/cpuidle.c:230)
kern :warn : [ 183.820550] ? lockdep_hardirqs_on (kernel/locking/lockdep.c:3395 kernel/locking/lockdep.c:3440)
kern :warn : [ 183.820551] ? rcu_idle_exit (arch/x86/include/asm/irqflags.h:41 (discriminator 2) arch/x86/include/asm/irqflags.h:84 (discriminator 2) kernel/rcu/tree.c:775 (discriminator 2))
kern :warn : [ 183.820551] ? trace_hardirqs_on (kernel/trace/trace_preemptirq.c:32 (discriminator 38))
kern :warn : [ 183.820552] cpuidle_enter (include/linux/compiler.h:293 drivers/cpuidle/cpuidle.c:352)
kern :warn : [ 183.820552] cpuidle_idle_call (kernel/sched/idle.c:117 kernel/sched/idle.c:207)
kern :warn : [ 183.820552] ? arch_cpu_idle_exit+0x40/0x40
kern :warn : [ 183.820553] ? __kasan_check_read (mm/kasan/common.c:93)
kern :warn : [ 183.820553] do_idle (kernel/sched/idle.c:270)
kern :warn : [ 183.820554] cpu_startup_entry (kernel/sched/idle.c:361 (discriminator 1))
kern :warn : [ 183.820554] start_secondary (arch/x86/kernel/smpboot.c:272)
kern :warn : [ 183.820555] ? set_cpu_sibling_map (arch/x86/kernel/smpboot.c:212)
kern :warn : [ 183.820555] secondary_startup_64 (arch/x86/kernel/head_64.S:241)
kern :warn : [ 183.820556] =============================
kern :warn : [ 183.820556] WARNING: suspicious RCU usage
kern :warn : [ 183.820557] 5.4.119-20-g42c771b6dd50 #1 Not tainted
kern :warn : [ 183.820557] -----------------------------
kern :warn : [ 183.820558] include/linux/rcupdate.h:669 rcu_read_unlock() used illegally while idle!
kern :warn : [ 183.820559] other info that might help us debug this:
kern :warn : [ 183.820560] RCU used illegally from idle CPU!
kern :warn : [ 183.820560] rcu_scheduler_active = 2, debug_locks = 1
kern :warn : [ 183.820561] RCU used illegally from extended quiescent state!
kern :warn : [ 183.820561] 4 locks held by swapper/202/0:
kern :warn : [ 183.820561] #0: ffffffff85632b80 (console_lock){+.+.}, at: vprintk_emit (kernel/printk/printk.c:2023)
kern :warn : [ 183.820564] #1: ffffffff856326c0 (console_owner){-...}, at: console_unlock (kernel/printk/printk.c:2493)
kern :warn : [ 183.820566] #2: ffffffff85c97ff8 (printing_lock){....}, at: vt_console_print (drivers/tty/vt/vt.c:2966)
kern :warn : [ 183.820568] #3: ffffffff85656420 (rcu_read_lock){....}, at: __atomic_notifier_call_chain (kernel/notifier.c:185)
kern :warn : [ 183.820570] stack backtrace:
kern :warn : [ 183.820571] CPU: 202 PID: 0 Comm: swapper/202 Not tainted 5.4.119-20-g42c771b6dd50 #1
kern :warn : [ 183.820571] Call Trace:
kern :warn : [ 183.820571] dump_stack (lib/dump_stack.c:120)
kern :warn : [ 183.820572] lockdep_rcu_suspicious (kernel/locking/lockdep.c:5449)
kern :warn : [ 183.820572] __atomic_notifier_call_chain (include/linux/rcupdate.h:669 kernel/notifier.c:190)
kern :warn : [ 183.820573] atomic_notifier_call_chain (kernel/notifier.c:200)
kern :warn : [ 183.820573] vt_console_print (drivers/tty/vt/vt.c:3013)
kern :warn : [ 183.820574] ? serial8250_config_port (drivers/tty/serial/8250/8250_port.c:3166)
kern :warn : [ 183.820574] ? unblank_screen (drivers/tty/vt/vt.c:2955)
kern :warn : [ 183.820575] call_console_drivers+0x16c/0x2e0
kern :warn : [ 183.820575] console_unlock (kernel/printk/printk.c:2505)
kern :warn : [ 183.820575] ? console_unlock (kernel/printk/printk.c:2493)
kern :warn : [ 183.820576] ? __down_trylock_console_sem (kernel/printk/printk.c:243)
kern :warn : [ 183.820576] ? vprintk_emit (kernel/printk/printk.c:2023)
kern :warn : [ 183.820577] vprintk_emit (kernel/printk/printk.c:2024)
kern :warn : [ 183.820577] vprintk_default (kernel/printk/printk.c:2054)
kern :warn : [ 183.820578] vprintk_func (kernel/printk/printk_safe.c:394)
kern :warn : [ 183.820578] ? trace_hardirqs_off (kernel/trace/trace_preemptirq.c:46)
kern :warn : [ 183.820578] printk (kernel/printk/printk.c:2079)
kern :warn : [ 183.820579] ? log_store.cold (kernel/printk/printk.c:2079)
kern :warn : [ 183.820579] ? tick_nohz_next_event (kernel/time/tick-sched.c:717)
kern :warn : [ 183.820580] ? tick_nohz_restart (kernel/time/tick-sched.c:661)
kern :warn : [ 183.820580] ? trace_hardirqs_on_thunk (arch/x86/entry/thunk_64.S:41)
kern :warn : [ 183.820581] ? trace_hardirqs_on_caller (kernel/trace/trace_preemptirq.c:60 (discriminator 38))
kern :warn : [ 183.820581] ? __kasan_check_read (mm/kasan/common.c:93)
kern :warn : [ 183.820582] ? rcu_is_watching (include/linux/compiler.h:266 arch/x86/include/asm/atomic.h:31 include/asm-generic/atomic-instrumented.h:27 kernel/rcu/tree.c:301 kernel/rcu/tree.c:908)
kern :warn : [ 183.820582] lockdep_rcu_suspicious (kernel/locking/lockdep.c:5411)
kern :warn : [ 183.820582] trace_tlb_flush (include/trace/events/tlb.h:38 include/trace/events/tlb.h:38)
kern :warn : [ 183.820583] switch_mm_irqs_off (arch/x86/mm/tlb.c:430)
kern :warn : [ 183.820583] ? trace_hardirqs_off (kernel/trace/trace_preemptirq.c:46)
kern :warn : [ 183.820584] leave_mm (arch/x86/mm/tlb.c:161 arch/x86/mm/tlb.c:150)
kern :warn : [ 183.820584] cpuidle_enter_state (drivers/cpuidle/cpuidle.c:230)
kern :warn : [ 183.820585] ? lockdep_hardirqs_on (kernel/locking/lockdep.c:3395 kernel/locking/lockdep.c:3440)
kern :warn : [ 183.820585] ? rcu_idle_exit (arch/x86/include/asm/irqflags.h:41 (discriminator 2) arch/x86/include/asm/irqflags.h:84 (discriminator 2) kernel/rcu/tree.c:775 (discriminator 2))
kern :warn : [ 183.820585] ? trace_hardirqs_on (kernel/trace/trace_preemptirq.c:32 (discriminator 38))
kern :warn : [ 183.820586] cpuidle_enter (include/linux/compiler.h:293 drivers/cpuidle/cpuidle.c:352)
kern :warn : [ 183.820586] cpuidle_idle_call (kernel/sched/idle.c:117 kernel/sched/idle.c:207)
kern :warn : [ 183.820587] ? arch_cpu_idle_exit+0x40/0x40
kern :warn : [ 183.820587] ? __kasan_check_read (mm/kasan/common.c:93)
kern :warn : [ 183.820587] do_idle (kernel/sched/idle.c:270)
kern :warn : [ 183.820588] cpu_startup_entry (kernel/sched/idle.c:361 (discriminator 1))
kern :warn : [ 183.820588] start_secondary (arch/x86/kernel/smpboot.c:272)
kern :warn : [ 183.820589] ? set_cpu_sibling_map (arch/x86/kernel/smpboot.c:212)
kern :warn : [ 183.820589] secondary_startup_64 (arch/x86/kernel/head_64.S:241)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240430/202404301635.1294804e-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-30 9:03 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=202404301635.1294804e-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=aurelianliu@tencent.com \
--cc=frankjpliu@tencent.com \
--cc=jason.zeng@intel.com \
--cc=jasperwang@tencent.com \
--cc=kaixuxia@tencent.com \
--cc=kasong@tencent.com \
--cc=kernelxing@tencent.com \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=pei.p.jia@intel.com \
--cc=sagazchen@tencent.com \
--cc=wu.zheng@intel.com \
--cc=yingbao.jia@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 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.