[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9afad2b3-38a5-470d-a66f-10aa2cba3bab@broadcom.com>
Date: Mon, 15 Apr 2024 10:36:37 -0700
From: Justin Chen <justin.chen@...adcom.com>
To: Markus Elfring <Markus.Elfring@....de>,
bcm-kernel-feedback-list@...adcom.com, netdev@...r.kernel.org,
kernel-janitors@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Florian Fainelli <florian.fainelli@...adcom.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>
Subject: Re: [PATCH net] net: bcmasp: fix memory leak when bringing down if
On 4/14/24 4:23 AM, Markus Elfring wrote:
> Can it be nicer to use the word “interface” instead of “if”
> in the summary phrase?
>
"if" for interface is a term used in the network stack, but I can see
why it is confusing. Can submit a v2.
>
>> When bringing down the TX rings we flush the rings but forget to
>> reclaimed the flushed packets. This lead to a memory leak since we
>> do not free the dma mapped buffers. …
>
> I find this change description improvable.
>
> * How do you think about to avoid typos?
>
> * Would another imperative wording be more desirable?
>
The change description makes sense to me. Can you be a bit more specific
as to what isn't clear here?
Thanks,
Justin
> Regards,
> Markus
Download attachment "smime.p7s" of type "application/pkcs7-signature" (4206 bytes)
Powered by blists - more mailing lists