[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MW4PR11MB5911A86FD4BDA2D38651A5ACBAB32@MW4PR11MB5911.namprd11.prod.outlook.com>
Date: Fri, 2 Aug 2024 00:22:34 +0000
From: "Singh, Krishneil K" <krishneil.k.singh@...el.com>
To: Simon Horman <horms@...nel.org>, "Lobakin, Aleksander"
<aleksander.lobakin@...el.com>
CC: "Linga, Pavan Kumar" <pavan.kumar.linga@...el.com>, "NEX SW NCIS OSDT ITP
Upstreaming" <nex.sw.ncis.osdt.itp.upstreaming@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>, Eric Dumazet
<edumazet@...gle.com>, "Kubiak, Michal" <michal.kubiak@...el.com>, "Nguyen,
Anthony L" <anthony.l.nguyen@...el.com>, Jakub Kicinski <kuba@...nel.org>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>, "Paolo
Abeni" <pabeni@...hat.com>, "David S. Miller" <davem@...emloft.net>
Subject: RE: [Intel-wired-lan] [PATCH iwl-net 2/3] idpf: fix memleak in vport
interrupt configuration
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@...osl.org> On Behalf Of
> Simon Horman
> Sent: Friday, July 26, 2024 9:16 AM
> To: Lobakin, Aleksander <aleksander.lobakin@...el.com>
> Cc: Linga, Pavan Kumar <pavan.kumar.linga@...el.com>; NEX SW NCIS OSDT ITP
> Upstreaming <nex.sw.ncis.osdt.itp.upstreaming@...el.com>;
> netdev@...r.kernel.org; linux-kernel@...r.kernel.org; stable@...r.kernel.org;
> Eric Dumazet <edumazet@...gle.com>; Kubiak, Michal
> <michal.kubiak@...el.com>; Nguyen, Anthony L
> <anthony.l.nguyen@...el.com>; Jakub Kicinski <kuba@...nel.org>; intel-wired-
> lan@...ts.osuosl.org; Paolo Abeni <pabeni@...hat.com>; David S. Miller
> <davem@...emloft.net>
> Subject: Re: [Intel-wired-lan] [PATCH iwl-net 2/3] idpf: fix memleak in vport
> interrupt configuration
>
> On Wed, Jul 24, 2024 at 03:40:23PM +0200, Alexander Lobakin wrote:
> > From: Michal Kubiak <michal.kubiak@...el.com>
> >
> > The initialization of vport interrupt consists of two functions:
> > 1) idpf_vport_intr_init() where a generic configuration is done
> > 2) idpf_vport_intr_req_irq() where the irq for each q_vector is
> > requested.
> >
> > The first function used to create a base name for each interrupt using
> > "kasprintf()" call. Unfortunately, although that call allocated memory
> > for a text buffer, that memory was never released.
> >
> > Fix this by removing creating the interrupt base name in 1).
> > Instead, always create a full interrupt name in the function 2), because
> > there is no need to create a base name separately, considering that the
> > function 2) is never called out of idpf_vport_intr_init() context.
> >
> > Fixes: d4d558718266 ("idpf: initialize interrupts and enable vport")
> > Cc: stable@...r.kernel.org # 6.7
> > Signed-off-by: Michal Kubiak <michal.kubiak@...el.com>
> > Reviewed-by: Pavan Kumar Linga <pavan.kumar.linga@...el.com>
> > Signed-off-by: Alexander Lobakin <aleksander.lobakin@...el.com>
>
> Reviewed-by: Simon Horman <horms@...nel.org>
Tested-by: Krishneil Singh <krishneil.k.singh@...el.com>
Powered by blists - more mailing lists