netdev - [PATCH iwl-net v2 0/2] ixgbe: fix aci.lock issues

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250908112629.1938159-1-jedrzej.jagielski@intel.com>
Date: Mon,  8 Sep 2025 13:26:27 +0200
From: Jedrzej Jagielski <jedrzej.jagielski@...el.com>
To: intel-wired-lan@...ts.osuosl.org
Cc: anthony.l.nguyen@...el.com,
	netdev@...r.kernel.org,
	Jedrzej Jagielski <jedrzej.jagielski@...el.com>
Subject: [PATCH iwl-net v2 0/2] ixgbe: fix aci.lock issues

There are 2 mutex (aci.lock) issues in ixgbe driver:
1) call trace on load - addressed by the 1st patch
2) call trace on unload - uncovered by the 1st patch and fixed by the
   2nd one

Both issues are highlighted by the commit 337369f8ce9e
("locking/mutex: Add MUTEX_WARN_ON() into fast path") and appear only
when CONFIG_DEBUG_MUTEXES flag is set.

Jedrzej Jagielski (2):
  ixgbe: initialize aci.lock before it's used
  ixgbe: destroy aci.lock later within ixgbe_remove path
---
v2: introduce additional patch in order to fix call trace appearing  after
applying 1st patch - call trace on reload
---
 drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 22 ++++++++++---------
 1 file changed, 12 insertions(+), 10 deletions(-)

-- 
2.31.1