lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <202501221104.9fe82ac4-lkp@intel.com>
Date: Wed, 22 Jan 2025 12:47:20 +0800
From: kernel test robot <oliver.sang@...el.com>
To: Russell King <rmk+kernel@...linux.org.uk>
CC: <oe-lkp@...ts.linux.dev>, <lkp@...el.com>, Jakub Kicinski
	<kuba@...nel.org>, Jacob Keller <jacob.e.keller@...el.com>,
	<netdev@...r.kernel.org>, <oliver.sang@...el.com>
Subject: [linux-next:master] [net]  03abf2a7c6: WARNING:suspicious_RCU_usage



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/next/linux-next.git master

[test failed on linux-next/master f066b5a6c7a06adfb666b7652cc99b4ff264f4ed]

in testcase: boot

config: i386-randconfig-141-20250120
compiler: clang-19
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          | 12         |
| drivers/net/phy/phy_device.c:#suspicious_rcu_dereference_protected()usage | 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@...el.com>
| Closes: https://lore.kernel.org/oe-lkp/202501221104.9fe82ac4-lkp@intel.com


[    9.233895][    T7] WARNING: suspicious RCU usage
[    9.234510][    T7] 6.13.0-rc7-01139-g03abf2a7c654 #1 Tainted: G                T
[    9.235566][    T7] -----------------------------
[    9.236305][    T7] drivers/net/phy/phy_device.c:2004 suspicious rcu_dereference_protected() usage!
[    9.237605][    T7]
[    9.237605][    T7] other info that might help us debug this:
[    9.237605][    T7]
[    9.239057][    T7]
[    9.239057][    T7] rcu_scheduler_active = 2, debug_locks = 1
[    9.240153][    T7] 4 locks held by kworker/u4:0/7:
[ 9.240882][ T7] #0: c5111cc0 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work (kernel/workqueue.c:3211) 
[ 9.242349][ T7] #1: c951bef0 (deferred_probe_work){+.+.}-{0:0}, at: process_one_work (kernel/workqueue.c:?) 
[ 9.243712][ T7] #2: c75e6c80 (&dev->mutex){....}-{4:4}, at: __device_attach (drivers/base/dd.c:1006) 
[ 9.244868][ T7] #3: c3f31254 (dsa2_mutex){+.+.}-{4:4}, at: dsa_register_switch (net/dsa/dsa.c:1499) 
[    9.246218][    T7]
[    9.246218][    T7] stack backtrace:
[    9.247150][    T7] CPU: 0 UID: 0 PID: 7 Comm: kworker/u4:0 Tainted: G                T  6.13.0-rc7-01139-g03abf2a7c654 #1
[    9.248636][    T7] Tainted: [T]=RANDSTRUCT
[    9.249165][    T7] Workqueue: events_unbound deferred_probe_work_func
[    9.250080][    T7] Call Trace:
[ 9.250503][ T7] dump_stack_lvl (lib/dump_stack.c:? lib/dump_stack.c:120) 
[ 9.251092][ T7] dump_stack (lib/dump_stack.c:129) 
[ 9.251610][ T7] lockdep_rcu_suspicious (kernel/locking/lockdep.c:6846) 
[ 9.252284][ T7] phy_detach (drivers/net/phy/phy_device.c:2004) 
[ 9.252804][ T7] phylink_connect_phy (drivers/net/phy/phylink.c:?) 
[ 9.253421][ T7] dsa_user_create (net/dsa/user.c:2657) 
[ 9.254067][ T7] dsa_port_setup (net/dsa/dsa.c:523) 
[ 9.254648][ T7] dsa_register_switch (net/dsa/dsa.c:759 net/dsa/dsa.c:888 net/dsa/dsa.c:1525 net/dsa/dsa.c:1539) 
[ 9.255298][ T7] dsa_loop_drv_probe (drivers/net/dsa/dsa_loop.c:343) 
[ 9.255927][ T7] mdio_probe (drivers/net/phy/mdio_device.c:166) 
[ 9.256445][ T7] really_probe (drivers/base/dd.c:581) 
[ 9.257004][ T7] __driver_probe_device (drivers/base/dd.c:800) 
[ 9.257624][ T7] ? lockdep_hardirqs_on_prepare (kernel/locking/lockdep.c:? kernel/locking/lockdep.c:4406) 
[ 9.258384][ T7] ? trace_hardirqs_on (kernel/trace/trace_preemptirq.c:80) 
[ 9.259006][ T7] driver_probe_device (drivers/base/dd.c:830) 
[ 9.259624][ T7] __device_attach_driver (drivers/base/dd.c:959) 
[ 9.260257][ T7] ? coredump_store (drivers/base/dd.c:922) 
[ 9.260846][ T7] bus_for_each_drv (drivers/base/bus.c:459) 
[ 9.261459][ T7] __device_attach (drivers/base/dd.c:1030) 
[ 9.274224][ T7] ? coredump_store (drivers/base/dd.c:922) 
[ 9.274849][ T7] device_initial_probe (drivers/base/dd.c:1080) 
[ 9.275481][ T7] bus_probe_device (drivers/base/bus.c:536) 
[ 9.276057][ T7] deferred_probe_work_func (drivers/base/dd.c:124) 
[ 9.276734][ T7] process_one_work (kernel/workqueue.c:3241) 
[ 9.277401][ T7] worker_thread (kernel/workqueue.c:3311 kernel/workqueue.c:3398) 
[ 9.278006][ T7] kthread (kernel/kthread.c:391) 
[ 9.278532][ T7] ? worker_attach_to_pool (kernel/workqueue.c:3344) 
[ 9.279213][ T7] ? kthread_blkcg (kernel/kthread.c:342) 
[ 9.279803][ T7] ? kthread_blkcg (kernel/kthread.c:342) 
[ 9.280398][ T7] ret_from_fork (arch/x86/kernel/process.c:153) 
[ 9.280951][ T7] ret_from_fork_asm (arch/x86/entry/entry_32.S:737) 
[ 9.281536][ T7] entry_INT80_32 (arch/x86/entry/entry_32.S:945) 
[    9.282546][    T7] dsa-loop fixed-0:1f lan1 (uninitialized): failed to connect to PHY: -EPERM
[    9.283900][    T7] dsa-loop fixed-0:1f lan1 (uninitialized): error -1 setting up PHY for tree 0, switch 0, port 0
[    9.285629][    T7] dsa-loop fixed-0:1f lan2 (uninitialized): PHY [dsa-0.0:01] driver [Generic PHY] (irq=POLL)
[    9.287170][    T7] dsa-loop fixed-0:1f lan2 (uninitialized): failed to connect to PHY: -EPERM
[    9.288436][    T7] dsa-loop fixed-0:1f lan2 (uninitialized): error -1 setting up PHY for tree 0, switch 0, port 1
[    9.290098][    T7] dsa-loop fixed-0:1f lan3 (uninitialized): PHY [dsa-0.0:02] driver [Generic PHY] (irq=POLL)
[    9.291626][    T7] dsa-loop fixed-0:1f lan3 (uninitialized): failed to connect to PHY: -EPERM
[    9.292898][    T7] dsa-loop fixed-0:1f lan3 (uninitialized): error -1 setting up PHY for tree 0, switch 0, port 2
[    9.294593][    T7] dsa-loop fixed-0:1f lan4 (uninitialized): PHY [dsa-0.0:03] driver [Generic PHY] (irq=POLL)
[    9.296110][    T7] dsa-loop fixed-0:1f lan4 (uninitialized): failed to connect to PHY: -EPERM
[    9.297398][    T7] dsa-loop fixed-0:1f lan4 (uninitialized): error -1 setting up PHY for tree 0, switch 0, port 3
[    9.299343][    T7] DSA: tree 0 setup
[    9.299993][    T7] 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/20250122/202501221104.9fe82ac4-lkp@intel.com



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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ