From: Simon Horman <horms@kernel.org>
To: Chenyuan Yang <chenyuan0y@gmail.com>
Cc: ecree.xilinx@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com, sdf@fomichev.me,
martinh@xilinx.com, netdev@vger.kernel.org,
linux-net-drivers@amd.com, bpf@vger.kernel.org,
zzjas98@gmail.com
Subject: Re: [PATCH] sfc: siena: handle NULL returned by xdp_convert_buff_to_frame()
Date: Fri, 25 Jul 2025 10:34:01 +0100 [thread overview]
Message-ID: <20250725093401.GA1367887@horms.kernel.org> (raw)
In-Reply-To: <20250723003230.1243224-1-chenyuan0y@gmail.com>
On Tue, Jul 22, 2025 at 07:32:30PM -0500, Chenyuan Yang wrote:
> The xdp_convert_buff_to_frame() function can return NULL when there is
> insufficient headroom in the buffer to store the xdp_frame structure
> or when the driver didn't reserve enough tailroom for skb_shared_info.
>
> Currently, the sfc siena driver does not check for this NULL return value
> in the XDP_TX case within efx_do_xdp().
>
> Fix by adding a proper NULL check in the XDP_TX case. If conversion
> fails, free the RX buffer and increment the bad drops counter, following
> the same pattern used for other XDP error conditions in this driver.
>
> Signed-off-by: Chenyuan Yang <chenyuan0y@gmail.com>
> Fixes: d48523cb88e0 ("sfc: Copy shared files needed for Siena (part 2)")
> ---
> drivers/net/ethernet/sfc/siena/rx.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/net/ethernet/sfc/siena/rx.c b/drivers/net/ethernet/sfc/siena/rx.c
> index 98d3c0743c0f..65f6daad3168 100644
> --- a/drivers/net/ethernet/sfc/siena/rx.c
> +++ b/drivers/net/ethernet/sfc/siena/rx.c
> @@ -310,6 +310,12 @@ static bool efx_do_xdp(struct efx_nic *efx, struct efx_channel *channel,
> case XDP_TX:
> /* Buffer ownership passes to tx on success. */
> xdpf = xdp_convert_buff_to_frame(&xdp);
> + if (unlikely(!xdpf)) {
> + efx_siena_free_rx_buffers(rx_queue, rx_buf, 1);
> + channel->n_rx_xdp_bad_drops++;
> + break;
> + }
I see the incidence of this cleanup code multiplying in this function.
I would be nice to follow-up by consolidating that - I'd suggest
in the form of a goto label at the end of the function.
But as a fix for net this minimal patch seems appropriate to me.
Reviewed-by: Simon Horman <horms@kernel.org>
> +
> err = efx_siena_xdp_tx_buffers(efx, 1, &xdpf, true);
> if (unlikely(err != 1)) {
> efx_siena_free_rx_buffers(rx_queue, rx_buf, 1);
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2025-07-25 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 0:32 [PATCH] sfc: siena: handle NULL returned by xdp_convert_buff_to_frame() Chenyuan Yang
2025-07-25 9:34 ` Simon Horman [this message]
2025-07-25 9:39 ` Simon Horman
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=20250725093401.GA1367887@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenyuan0y@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=martinh@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=zzjas98@gmail.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).