From: Simon Horman <simon.horman@corigine.com>
To: 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 v3] net: amd: Fix link leak when verifying config failed
Date: Sun, 23 Apr 2023 20:48:52 +0200 [thread overview]
Message-ID: <ZEV9lKkZBiTiIjjl@corigine.com> (raw)
In-Reply-To: <20230421183304.155460-1-gangecen@hust.edu.cn>
On Sat, Apr 22, 2023 at 02:33:03AM +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.
>
> Fixes: 2b3af54dc373 ("net: amd: Fix link leak when verifying config failed")
Perhaps it would be better to remove the driver.
Perhaps we can take this fix then consider removing it.
But if we do move forwards with this patch then
I suggest the fixes tag should that below, as:
a) The problem seems to have been present since the beginning of git
history; and
b) The commit above doesn't seem to exist in net or net-next
(I assume it's a local commit id of this patch)
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Gan Gecen <gangecen@hust.edu.cn>
> Reviewed-by: Paolo Abeni <pabeni@redhat.com>
> ---
> v2->v3: Add Fixes tag and add a suggestion about this driver.
> 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-23 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 18:33 [PATCH v3] net: amd: Fix link leak when verifying config failed Gencen Gan
2023-04-23 18:48 ` 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=ZEV9lKkZBiTiIjjl@corigine.com \
--to=simon.horman@corigine.com \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).