netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Russell King <rmk+kernel@armlinux.org.uk>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>, Jakub Kicinski <kuba@kernel.org>,
	Jacob Keller <jacob.e.keller@intel.com>, <netdev@vger.kernel.org>,
	<oliver.sang@intel.com>
Subject: [linus:master] [net]  03abf2a7c6: WARNING:suspicious_RCU_usage
Date: Wed, 5 Feb 2025 14:08:04 +0800	[thread overview]
Message-ID: <202502051331.7587ac82-lkp@intel.com> (raw)



Hello,

kernel test robot noticed "WARNING:suspicious_RCU_usage" on:

commit: 03abf2a7c65451e663b078b0ed1bfa648cd9380f ("net: phylink: add EEE management")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

[test failed on linus/master      5c8c229261f14159b54b9a32f12e5fa89d88b905]
[test failed on linux-next/master 40b8e93e17bff4a4e0cc129e04f9fdf5daa5397e]

in testcase: trinity
version: trinity-i386-abe9de86-1_20230429
with following parameters:

	runtime: 300s
	group: group-02
	nr_groups: 5



config: i386-randconfig-051-20250203
compiler: gcc-12
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G

(please refer to attached dmesg/kmsg for entire log/backtrace)


+---------------------------------------------------------------------------+------------+------------+
|                                                                           | a17ceec62f | 03abf2a7c6 |
+---------------------------------------------------------------------------+------------+------------+
| WARNING:suspicious_RCU_usage                                              | 0          | 36         |
| drivers/net/phy/phy_device.c:#suspicious_rcu_dereference_protected()usage | 0          | 36         |
+---------------------------------------------------------------------------+------------+------------+


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/202502051331.7587ac82-lkp@intel.com


[   19.591040][   T22] WARNING: suspicious RCU usage
[   19.592068][   T22] 6.13.0-rc7-01139-g03abf2a7c654 #1 Tainted: G S              T
[   19.593703][   T22] -----------------------------
[   19.594724][   T22] drivers/net/phy/phy_device.c:2004 suspicious rcu_dereference_protected() usage!
[   19.596546][   T22]
[   19.596546][   T22] other info that might help us debug this:
[   19.596546][   T22]
[   19.598680][   T22]
[   19.598680][   T22] rcu_scheduler_active = 2, debug_locks = 1
[   19.600338][   T22] 4 locks held by kworker/u4:1/22:
[ 19.601463][ T22] #0: c7d1e6b0 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work (kernel/workqueue.c:3211) 
[ 19.603512][ T22] #1: c512bf30 (deferred_probe_work){+.+.}-{0:0}, at: process_one_work (kernel/workqueue.c:3212) 
[ 19.605344][ T22] #2: c8d1da78 (&dev->mutex){....}-{4:4}, at: device_lock (include/linux/device.h:1015) 
[ 19.610278][ T22] #3: c3fba014 (dsa2_mutex){+.+.}-{4:4}, at: dsa_register_switch (net/dsa/dsa.c:1499 net/dsa/dsa.c:1539) 
[   19.612136][   T22]
[   19.612136][   T22] stack backtrace:
[   19.613434][   T22] CPU: 0 UID: 0 PID: 22 Comm: kworker/u4:1 Tainted: G S              T  6.13.0-rc7-01139-g03abf2a7c654 #1 0503d02651d90c323d4064ac27ee9898a6e76f3e
[   19.616145][   T22] Tainted: [S]=CPU_OUT_OF_SPEC, [T]=RANDSTRUCT
[   19.617319][   T22] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[   19.619218][   T22] Workqueue: events_unbound deferred_probe_work_func
[   19.620457][   T22] Call Trace:
[ 19.621167][ T22] dump_stack_lvl (lib/dump_stack.c:123) 
[ 19.622090][ T22] dump_stack (lib/dump_stack.c:130) 
[ 19.622924][ T22] lockdep_rcu_suspicious (kernel/locking/lockdep.c:6846) 
[ 19.623932][ T22] phy_detach (drivers/net/phy/phy_device.c:2004 (discriminator 9)) 
[ 19.624755][ T22] phylink_connect_phy (drivers/net/phy/phylink.c:2327) 
[ 19.625475][ T22] dsa_user_create (net/dsa/user.c:2620 net/dsa/user.c:2655 net/dsa/user.c:2790) 
[ 19.626083][ T22] dsa_port_setup (net/dsa/dsa.c:519) 
[ 19.626631][ T22] dsa_tree_setup (net/dsa/dsa.c:759 net/dsa/dsa.c:888) 
[ 19.627196][ T22] ? dsa_switch_parse_ports (net/dsa/dsa.c:1440) 
[ 19.627844][ T22] dsa_register_switch (net/dsa/dsa.c:1525 net/dsa/dsa.c:1539) 
[ 19.628455][ T22] ? dev_get_by_name (net/core/dev.c:881) 
[ 19.629080][ T22] dsa_loop_drv_probe (drivers/net/dsa/dsa_loop.c:343) 
[ 19.629973][ T22] mdio_probe (drivers/net/phy/mdio_device.c:165) 
[ 19.630762][ T22] really_probe (drivers/base/dd.c:579 drivers/base/dd.c:658) 
[ 19.631583][ T22] __driver_probe_device (drivers/base/dd.c:800) 
[ 19.632519][ T22] driver_probe_device (drivers/base/dd.c:830) 
[ 19.633287][ T22] __device_attach_driver (drivers/base/dd.c:958) 
[ 19.633903][ T22] bus_for_each_drv (drivers/base/bus.c:459) 
[ 19.634466][ T22] __device_attach (drivers/base/dd.c:1032) 
[ 19.635018][ T22] ? driver_probe_device (drivers/base/dd.c:922) 
[ 19.635627][ T22] device_initial_probe (drivers/base/dd.c:1080) 
[ 19.636222][ T22] bus_probe_device (drivers/base/bus.c:536) 
[ 19.636783][ T22] deferred_probe_work_func (drivers/base/dd.c:124) 
[ 19.637569][ T22] process_one_work (include/trace/events/workqueue.h:110 include/trace/events/workqueue.h:110 kernel/workqueue.c:3241) 
[ 19.638328][ T22] ? __list_add (include/linux/list.h:150) 
[ 19.639013][ T22] process_scheduled_works (kernel/workqueue.c:3317) 
[ 19.639878][ T22] worker_thread (include/linux/list.h:373 kernel/workqueue.c:946 kernel/workqueue.c:3399) 
[ 19.640635][ T22] kthread (kernel/kthread.c:391) 
[ 19.641303][ T22] ? rescuer_thread (kernel/workqueue.c:3344) 
[ 19.642153][ T22] ? list_del_init (include/linux/posix-timers.h:225) 
[ 19.643006][ T22] ret_from_fork (arch/x86/kernel/process.c:153) 
[ 19.643818][ T22] ? list_del_init (include/linux/posix-timers.h:225) 
[ 19.644555][ T22] ret_from_fork_asm (arch/x86/entry/entry_32.S:737) 
[ 19.645201][ T22] entry_INT80_32 (arch/x86/entry/entry_32.S:945) 
[   19.646149][   T22] dsa-loop fixed-0:1f lan1 (uninitialized): failed to connect to PHY: -EPERM
[   19.647542][   T22] dsa-loop fixed-0:1f lan1 (uninitialized): error -1 setting up PHY for tree 0, switch 0, port 0
[   19.649283][   T22] dsa-loop fixed-0:1f lan2 (uninitialized): PHY [dsa-0.0:01] driver [Generic PHY] (irq=POLL)
[   19.650853][   T22] dsa-loop fixed-0:1f lan2 (uninitialized): failed to connect to PHY: -EPERM
[   19.652238][   T22] dsa-loop fixed-0:1f lan2 (uninitialized): error -1 setting up PHY for tree 0, switch 0, port 1
[   19.653856][   T22] dsa-loop fixed-0:1f lan3 (uninitialized): PHY [dsa-0.0:02] driver [Generic PHY] (irq=POLL)
[   19.655392][   T22] dsa-loop fixed-0:1f lan3 (uninitialized): failed to connect to PHY: -EPERM
[   19.656689][   T22] dsa-loop fixed-0:1f lan3 (uninitialized): error -1 setting up PHY for tree 0, switch 0, port 2
[   19.658308][   T22] dsa-loop fixed-0:1f lan4 (uninitialized): PHY [dsa-0.0:03] driver [Generic PHY] (irq=POLL)
[   19.659841][   T22] dsa-loop fixed-0:1f lan4 (uninitialized): failed to connect to PHY: -EPERM
[   19.661168][   T22] dsa-loop fixed-0:1f lan4 (uninitialized): error -1 setting up PHY for tree 0, switch 0, port 3
[   19.663018][   T22] DSA: tree 0 setup
[   19.663591][   T22] dsa-loop fixed-0:1f: DSA mockup driver: 0x1f



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250205/202502051331.7587ac82-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


             reply	other threads:[~2025-02-05  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05  6:08 kernel test robot [this message]
2025-02-05 17:19 ` [linus:master] [net] 03abf2a7c6: WARNING:suspicious_RCU_usage Russell King (Oracle)
2025-03-27 13:09   ` Kory Maincent

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=202502051331.7587ac82-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=jacob.e.keller@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=oe-lkp@lists.linux.dev \
    --cc=rmk+kernel@armlinux.org.uk \
    /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).