From: Dongliang Mu <dzm91@hust.edu.cn>
To: Simon Horman <simon.horman@corigine.com>,
Gencen Gan <gangecen@hust.edu.cn>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
hust-os-kernel-patches@googlegroups.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] net: amd: Fix link leak when verifying config failed
Date: Mon, 24 Apr 2023 21:28:59 +0800 [thread overview]
Message-ID: <6df17c8d-1ed3-6059-e821-bd58e370c641@hust.edu.cn> (raw)
In-Reply-To: <ZEZ9m4Q7qO0UTx1B@corigine.com>
On 4/24/23 21:01, Simon Horman wrote:
> On Mon, Apr 24, 2023 at 06:46:43PM +0800, Gencen Gan wrote:
>> After failing to verify configuration, it returns directly without
>> releasing link, which may cause memory leak.
>>
>> Paolo Abeni thinks that the whole code of this driver is quite
>> "suboptimal" and looks unmainatained since at least ~15y, so he
>> suggests that we could simply remove the whole driver, please
>> take it into consideration.
>>
>> Simon Horman suggests that the fix label should be set to
>> "Linux-2.6.12-rc2" considering that the problem has existed
>> since the driver was introduced and the commit above doesn't
>> seem to exist in net/net-next.
>>
>> Fixes: 99c3b0265649 ("Linux-2.6.12-rc2")
>
> Unless I'm mistaken, this should be:
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
>
>> Signed-off-by: Gan Gecen <gangecen@hust.edu.cn>
>> Reviewed-by: Paolo Abeni <pabeni@redhat.com>
>> Reviewed-by: Simon Horman <simon.horman@corigine.com>
>
> I think that tags such as Reviewed-by need to be given explicitly.
> And as the above two Reviewed-by tags were not, so it is a bit
> odd for them to appear above.
Hi Semon,
Sorry about the naive mistakes made by Gan Gecen. Our team had
repeatedly talked about this issue and written it in our kernel
contribution guidance.
[1]
https://groups.google.com/g/hust-os-kernel-patches/c/GThhx08kecg/m/5p61iz6KAQAJ
>
>> ---
>> v3->v4: modify the 'Fixes:' tag to make it more accurate.
>> drivers/net/ethernet/amd/nmclan_cs.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/ethernet/amd/nmclan_cs.c b/drivers/net/ethernet/amd/nmclan_cs.c
>> index 823a329a921f..0dd391c84c13 100644
>> --- a/drivers/net/ethernet/amd/nmclan_cs.c
>> +++ b/drivers/net/ethernet/amd/nmclan_cs.c
>> @@ -651,7 +651,7 @@ static int nmclan_config(struct pcmcia_device *link)
>> } else {
>> pr_notice("mace id not found: %x %x should be 0x40 0x?9\n",
>> sig[0], sig[1]);
>> - return -ENODEV;
>> + goto failed;
>> }
>> }
>>
>> --
>> 2.34.1
>>
>
prev parent reply other threads:[~2023-04-24 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 10:46 Gencen Gan
2023-04-24 13:01 ` Simon Horman
2023-04-24 13:28 ` Dongliang Mu [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=6df17c8d-1ed3-6059-e821-bd58e370c641@hust.edu.cn \
--to=dzm91@hust.edu.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gangecen@hust.edu.cn \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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
all inboxes | Powered by JetHome®