From: Simon Horman <horms@kernel.org>
To: Ashwin Gundarapu <linuxuser509@zohomail.in>
Cc: anthonylnguyen <anthony.l.nguyen@intel.com>,
"anthony.l.nguyen@intel.com" <przemyslaw.kitszel@intel.com>,
andrewnetdev <andrew+netdev@lunn.ch>, davem <davem@davemloft.net>,
edumazet <edumazet@google.com>, kuba <kuba@kernel.org>,
pabeni <pabeni@redhat.com>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] e1000e: fix memory leak of msix_entries on MSI-X failure
Date: Tue, 26 May 2026 21:01:14 +0100 [thread overview]
Message-ID: <20260526200114.GD2256768@horms.kernel.org> (raw)
In-Reply-To: <19e537fa55c.56218d6244367.1765806925055659075@zohomail.in>
On Sat, May 23, 2026 at 11:52:14AM +0530, Ashwin Gundarapu wrote:
> From: Ashwin Gundarapu <linuxuser509@zohomail.in>
> Date: Sat, 23 May 2026 11:49:40 +0530
> Subject: [PATCH] e1000e: fix memory leak of msix_entries on MSI-X failure
>
> When MSI-X initialization fails, the driver falls through to try
> MSI or legacy interrupts. However, the msix_entries array allocated
> earlier is not freed, causing a memory leak. Free it and set to
> NULL before falling through to the MSI fallback path.
>
> Found by code inspection.
>
> Signed-off-by: Ashwin Gundarapu <linuxuser509@zohomail.in>
> ---
> drivers/net/ethernet/intel/e1000e/netdev.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/e1000e/netdev.c b/drivers/net/ethernet/intel/e1000e/netdev.c
> index 7ce0cc8ab8f4..1526069d7fc1 100644
> --- a/drivers/net/ethernet/intel/e1000e/netdev.c
> +++ b/drivers/net/ethernet/intel/e1000e/netdev.c
> @@ -2065,10 +2065,12 @@ void e1000e_set_interrupt_capability(struct e1000_adapter *adapter)
> a->num_vectors);
> if (err > 0)
> return;
> - }
> - /* MSI-X failed, so fall through and try MSI */
> - e_err("Failed to initialize MSI-X interrupts. Falling back to MSI interrupts.\n");
> - e1000e_reset_interrupt_capability(adapter);
> + }
> + /* MSI-X failed, so fall through and try MSI */
> + e_err("Failed to initialize MSI-X interrupts. Falling back to MSI interrupts.\n");
> + kfree(adapter->msix_entries);
> + adapter->msix_entries = NULL;
> + e1000e_reset_interrupt_capability(adapter);
Hi Ashwin,
e1000e_reset_interrupt_capability() already handles freeing (and NULLing)
msix_entries, and it does so after calling pci_disable_msix().
This patch seems to have the effect of bypassing the call to
pci_disable_msix().
Are you sure this is fixing a memory leak as described?
Flagged by https://sashiko.dev/ and https://netdev-ai.bots.linux.dev/sashiko/
> }
> adapter->int_mode = E1000E_INT_MODE_MSI;
> fallthrough;
> --
> 2.43.0
>
>
prev parent reply other threads:[~2026-05-26 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 6:22 [PATCH net-next] e1000e: fix memory leak of msix_entries on MSI-X failure Ashwin Gundarapu
2026-05-25 8:41 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-05-26 20:01 ` Simon Horman [this message]
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=20260526200114.GD2256768@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxuser509@zohomail.in \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox