From: Simon Horman <horms@kernel.org>
To: Jian Zhang <zhangjian.3032@bytedance.com>
Cc: Samuel Mendoza-Jonas <sam@mendozajonas.com>,
Paul Fertser <fercerpav@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: ncsi: fix skb leak in error paths
Date: Wed, 4 Mar 2026 11:16:07 +0000 [thread overview]
Message-ID: <20260304111607.GH71509@kernel.org> (raw)
In-Reply-To: <20260302054629.1347119-1-zhangjian.3032@bytedance.com>
On Mon, Mar 02, 2026 at 01:46:29PM +0800, Jian Zhang wrote:
> Early return paths in NCSI RX and AEN handlers fail to release
> the received skb, resulting in a memory leak.
>
> Specifically, ncsi_aen_handler() returns on invalid AEN packets
> without consuming the skb. Similarly, ncsi_rcv_rsp() exits early
> when failing to resolve the NCSI device, response handler, or
> request, leaving the skb unfreed.
>
> Signed-off-by: Jian Zhang <zhangjian.3032@bytedance.com>
As fixes for Networking code these should have fixes tags.
I think the following are appropriate.
Fixes: 7a82ecf4cfb8 ("net/ncsi: NCSI AEN packet handler")
Fixes: 138635cc27c9 ("net/ncsi: NCSI response packet handler")
As they seem to be commits from the same patch-set,
included in the same release - v4.8-rc1, I think
we can keep this as a single patch.
If you agree then it shouldn't be necessary to post a new version because
of this, as patchwork should pick up the tags above. But for future
reference, assuming these are backporting candidates, it's best to CC
stable on bugfixes for net.
Overall, this looks good to me.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2026-03-04 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 5:46 [PATCH net] net: ncsi: fix skb leak in error paths Jian Zhang
2026-03-04 11:16 ` Simon Horman [this message]
2026-03-04 11:40 ` ByteDance
2026-03-05 0:45 ` Jakub Kicinski
2026-03-05 6:09 ` ByteDance
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=20260304111607.GH71509@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fercerpav@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sam@mendozajonas.com \
--cc=zhangjian.3032@bytedance.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