[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z1fdE6ftFMtVFeW5@mev-dev.igk.intel.com>
Date: Tue, 10 Dec 2024 07:17:55 +0100
From: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>
To: Maxim Levitsky <mlevitsk@...hat.com>
Cc: kvm@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Souradeep Chakrabarti <schakrabarti@...ux.microsoft.com>,
linux-hyperv@...r.kernel.org, Dexuan Cui <decui@...rosoft.com>,
Paolo Abeni <pabeni@...hat.com>, linux-kernel@...r.kernel.org,
Konstantin Taranov <kotaranov@...rosoft.com>,
Leon Romanovsky <leon@...nel.org>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Wei Liu <wei.liu@...nel.org>, Andrew Lunn <andrew+netdev@...n.ch>,
Shradha Gupta <shradhagupta@...ux.microsoft.com>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Eric Dumazet <edumazet@...gle.com>, Long Li <longli@...rosoft.com>,
Yury Norov <yury.norov@...il.com>
Subject: Re: [PATCH v2 1/2] net: mana: Fix memory leak in mana_gd_setup_irqs
On Tue, Dec 10, 2024 at 07:13:53AM +0100, Michal Swiatkowski wrote:
> On Mon, Dec 09, 2024 at 12:57:50PM -0500, Maxim Levitsky wrote:
> > Commit 8afefc361209 ("net: mana: Assigning IRQ affinity on HT cores")
> > added memory allocation in mana_gd_setup_irqs of 'irqs' but the code
> > doesn't free this temporary array in the success path.
> >
> > This was caught by kmemleak.
> >
> > Fixes: 8afefc361209 ("net: mana: Assigning IRQ affinity on HT cores")
> > Signed-off-by: Maxim Levitsky <mlevitsk@...hat.com>
> > ---
> > drivers/net/ethernet/microsoft/mana/gdma_main.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/net/ethernet/microsoft/mana/gdma_main.c b/drivers/net/ethernet/microsoft/mana/gdma_main.c
> > index e97af7ac2bb2..aba188f9f10f 100644
> > --- a/drivers/net/ethernet/microsoft/mana/gdma_main.c
> > +++ b/drivers/net/ethernet/microsoft/mana/gdma_main.c
> > @@ -1375,6 +1375,7 @@ static int mana_gd_setup_irqs(struct pci_dev *pdev)
> > gc->max_num_msix = nvec;
> > gc->num_msix_usable = nvec;
> > cpus_read_unlock();
> > + kfree(irqs);
>
> Ther is still memleak in case of jumping to free_irq_vector when
> gc->irq_contexts allocation is failing.
>
Ignore that, just took a look at second patch.
Reviewed-by: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>
> Thanks
> > return 0;
> >
> > free_irq:
> > --
> > 2.26.3
Powered by blists - more mailing lists