Netdev List
 help / color / mirror / Atom feed
From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Paul Moses <p@1g4.org>
Cc: <anthony.l.nguyen@intel.com>, <przemyslaw.kitszel@intel.com>,
	<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
	<edumazet@kernel.org>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<ast@kernel.org>, <daniel@iogearbox.net>, <hawk@kernel.org>,
	<john.fastabend@gmail.com>, <sdf@fomichev.me>,
	<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
	<bpf@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] igc: return XSK frame copies on XDP_TX failure
Date: Tue, 27 Oct 2026 09:19:18 +0100	[thread overview]
Message-ID: <auBehtniOJTRGfaD@boxer> (raw)
In-Reply-To: <HTx28-b95D5R6LIxwQGHksxNXb6wWbEOp6IGCfRU51shEKudZgRxqFylE-Ngqd3ufeFJGlo5VccF1yXfAVeWQlqpNoSMp5oxS8tlJNxH4h0=@1g4.org>

On Mon, Oct 26, 2026 at 10:18:03PM +0000, Paul Moses wrote:
> On Monday, October 26th, 2026 at 3:07 PM, Maciej Fijalkowski <maciej.fijalkowski@intel.com> wrote:
> 
> > On Fri, Oct 23, 2026 at 02:13:42PM +0000, Paul Moses wrote:
> > > Converting an XSK buffer to an XDP frame allocates a page and returns
> > > the original buffer to its pool. If the TX ring is full or DMA mapping
> > > fails, igc_xdp_xmit_back() returns an error without freeing the copy.
> > > The RX cleaner cannot release it, so the page leaks.
> > >
> > > Return the copied frame on TX failure. Save the RX memory type before
> > > conversion so native frames remain RX-owned on failure.
> > >
> > > Fixes: fc9df2a0b520 ("igc: Enable RX via AF_XDP zero-copy")
> > > Cc: stable@vger.kernel.org
> > > Signed-off-by: Paul Moses <p@1g4.org>
> > > ---
> > > Tested on Intel I225-V with baseline and patched kernels. Physical
> > > pause-frame backpressure caused 46 leaked copies on the baseline.
> > > With the fix, all 72 rejected copies were returned once and freed,
> > > and all 192 copies were accounted for.
> > >
> > >  drivers/net/ethernet/intel/igc/igc_main.c | 5 +++++
> > >  1 file changed, 5 insertions(+)
> > >
> > > diff --git a/drivers/net/ethernet/intel/igc/igc_main.c b/drivers/net/ethernet/intel/igc/igc_main.c
> > > index 1fb5f3cbe93c..39263fd04aa9 100644
> > > --- a/drivers/net/ethernet/intel/igc/igc_main.c
> > > +++ b/drivers/net/ethernet/intel/igc/igc_main.c
> > > @@ -2487,6 +2487,7 @@ struct igc_ring *igc_get_tx_ring(struct igc_adapter *adapter, int cpu)
> > >
> > >  static int igc_xdp_xmit_back(struct igc_adapter *adapter, struct xdp_buff *xdp)
> > >  {
> > > +	enum xdp_mem_type mem_type = xdp->rxq->mem.type;
> > 
> > small nit is we require a concept called RCT (reverse christmas tree)
> > which makes you to order variable declarations from longest line to
> > shortest.
> > 
> > >  	struct xdp_frame *xdpf = xdp_convert_buff_to_frame(xdp);
> > >  	int cpu = smp_processor_id();
> > >  	struct netdev_queue *nq;
> > > @@ -2504,6 +2505,10 @@ static int igc_xdp_xmit_back(struct igc_adapter *adapter, struct xdp_buff *xdp)
> > >  	txq_trans_cond_update(nq);
> > >  	res = igc_xdp_init_tx_descriptor(ring, xdpf);
> > >  	__netif_tx_unlock(nq);
> > > +
> > > +	if (res && mem_type == MEM_TYPE_XSK_BUFF_POOL)
> > > +		xdp_return_frame(xdpf);
> > 
> > Reviewed-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> > 
> > > +
> > >  	return res;
> > >  }
> > >
> > > --
> > > 2.56.GIT
> > >
> > >
> > >
> > 
> 
> Never know what to do in these cases, order matters here, so
> do I touch more lines to move the assignment down below?

	struct xdp_frame *xdpf = xdp_convert_buff_to_frame(xdp);
+	enum xdp_mem_type mem_type = xdp->rxq->mem.type;
	int cpu = smp_processor_id();
	struct netdev_queue *nq;

this would satisfy the RCT rule.

      reply	other threads:[~2026-10-27  8:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 14:13 [PATCH net] igc: return XSK frame copies on XDP_TX failure Paul Moses
2026-10-23 14:16 ` netdev-bot+sinfo
2026-10-26 20:05 ` Maciej Fijalkowski
2026-10-26 22:18   ` Paul Moses
2026-10-27  8:19     ` Maciej Fijalkowski [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=auBehtniOJTRGfaD@boxer \
    --to=maciej.fijalkowski@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=hawk@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=p@1g4.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=sdf@fomichev.me \
    /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