[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251211091636.57722-1-enjuk@amazon.com>
Date: Thu, 11 Dec 2025 18:15:30 +0900
From: Kohei Enju <enjuk@...zon.com>
To: <intel-wired-lan@...ts.osuosl.org>, <netdev@...r.kernel.org>
CC: Tony Nguyen <anthony.l.nguyen@...el.com>, Przemek Kitszel
<przemyslaw.kitszel@...el.com>, Andrew Lunn <andrew+netdev@...n.ch>, "David
S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, "Jakub
Kicinski" <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, "Jedrzej
Jagielski" <jedrzej.jagielski@...el.com>, Stefan Wegrzyn
<stefan.wegrzyn@...el.com>, Simon Horman <horms@...nel.org>, Jacob Keller
<jacob.e.keller@...el.com>, <kohei@...uk.org>, Kohei Enju <enjuk@...zon.com>
Subject: [PATCH iwl-net v2 0/2] ixgbe: fix issues around ixgbe_recovery_probe()
ixgbe_recovery_probe() and codes around this function have two bugs:
1. resource freeing up is not complete, resulting in memory leaks
2. mutex lock (hw->aci.lock) is initialized twice
Fix these issues.
Changes:
v2:
- let ixgbe_probe() to clean up, instead of ixgbe_recovery_probe()
- don't initialize aci lock twice
v1: https://lore.kernel.org/intel-wired-lan/20251206155146.95857-1-enjuk@amazon.com/
Kohei Enju (2):
ixgbe: fix memory leaks in the ixgbe_recovery_probe() path
ixgbe: don't initialize aci lock in ixgbe_recovery_probe()
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 26 +++++++------------
1 file changed, 10 insertions(+), 16 deletions(-)
--
2.52.0
Powered by blists - more mailing lists