From: Gerhard Engleder <gerhard@engleder-embedded.com>
To: Wang Hai <wanghai38@huawei.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
andreas@gaisler.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, kristoffer@gaisler.com
Subject: Re: [PATCH net] net: ethernet: aeroflex: fix potential memory leak in greth_start_xmit_gbit()
Date: Fri, 11 Oct 2024 22:41:31 +0200 [thread overview]
Message-ID: <3d26ab3e-2a3c-4c36-b165-06a1029bb0b0@engleder-embedded.com> (raw)
In-Reply-To: <20241011113908.43966-1-wanghai38@huawei.com>
On 11.10.24 13:39, Wang Hai wrote:
> The greth_start_xmit_gbit() returns NETDEV_TX_OK without freeing skb
> in case of skb->len being too long, add dev_kfree_skb() to fix it.
>
> Fixes: d4c41139df6e ("net: Add Aeroflex Gaisler 10/100/1G Ethernet MAC driver")
> Signed-off-by: Wang Hai <wanghai38@huawei.com>
> ---
> drivers/net/ethernet/aeroflex/greth.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ethernet/aeroflex/greth.c b/drivers/net/ethernet/aeroflex/greth.c
> index 27af7746d645..8f6835a710b9 100644
> --- a/drivers/net/ethernet/aeroflex/greth.c
> +++ b/drivers/net/ethernet/aeroflex/greth.c
> @@ -484,6 +484,7 @@ greth_start_xmit_gbit(struct sk_buff *skb, struct net_device *dev)
>
> if (unlikely(skb->len > MAX_FRAME_SIZE)) {
> dev->stats.tx_errors++;
> + dev_kfree_skb(skb);
> goto out;
dev_kfree_skb(skb) is already part of the error handling, one line above
the "out" label. Why don't you just add another label which includes
dev_kfree_skb(skb) and goto that label?
Gerhard
next prev parent reply other threads:[~2024-10-11 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 11:39 Wang Hai
2024-10-11 20:41 ` Gerhard Engleder [this message]
2024-10-12 11:16 ` Wang Hai
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=3d26ab3e-2a3c-4c36-b165-06a1029bb0b0@engleder-embedded.com \
--to=gerhard@engleder-embedded.com \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kristoffer@gaisler.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wanghai38@huawei.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®