mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Paul Moses <p@1g4.org>
Cc: <netdev@vger.kernel.org>, <magnus.karlsson@intel.com>,
	<sdf@fomichev.me>, <davem@davemloft.net>, <edumazet@kernel.org>,
	<kuba@kernel.org>, <pabeni@redhat.com>, <horms@kernel.org>,
	<bpf@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>
Subject: Re: [PATCH net] xsk: restore UMEM flags after failed pool assignment
Date: Thu, 22 Oct 2026 10:34:07 +0200	[thread overview]
Message-ID: <atnKf5dNv0Vk1sCo@boxer> (raw)
In-Reply-To: <20261021224705.2078753-1-p@1g4.org>

On Wed, Oct 21, 2026 at 10:47:33PM +0000, Paul Moses wrote:
> xp_assign_dev() sets XDP_UMEM_SG_FLAG before checking whether the
> device supports multibuffer zero-copy. If assignment fails, xsk_bind()
> destroys the pool but retains the registered UMEM. A subsequent bind
> without XDP_USE_SG inherits the stale flag.

so you opened a socket, tried binding with XDP_USE_SG, failed then retried
without the flag and you noticed unexpected rx frame size due to kept
XDP_UMEM_SG_FLAG - do i get this right?

socket not being closed kept the umem alive...

> 
> The flag also changes RX buffer sizing after DMA mapping. On igc, a
> failed SG bind followed by a non-SG retry with 4096-byte chunks and
> 1792 bytes of headroom passes admission with 2048 bytes, but programs
> a 1024-byte RX buffer. On I225-V hardware, an ordinary 1514-byte frame
> is truncated to 1024 bytes or 1008 with RX timestamps enabled.
> Restoring the original flags eliminates the truncation in both cases.

It should be enough to state that sg flag presence takes into account
tailroom size and therefore has influence on final rx frame size provided
to driver.

> 
> Save the UMEM flags before assignment and restore them on failure.

Regarding the patch content:
Acked-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>

> 
> Fixes: d609f3d228a8 ("xsk: add multi-buffer support for sockets sharing umem")
> Cc: stable@vger.kernel.org
> Signed-off-by: Paul Moses <p@1g4.org>
> ---
>  net/xdp/xsk_buff_pool.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/net/xdp/xsk_buff_pool.c b/net/xdp/xsk_buff_pool.c
> index 0ebd4d46f7ab..7750d2ec4ee2 100644
> --- a/net/xdp/xsk_buff_pool.c
> +++ b/net/xdp/xsk_buff_pool.c
> @@ -166,6 +166,7 @@ int xp_assign_dev(struct xsk_buff_pool *pool,
>  {
>  	u32 needed = netdev->mtu + ETH_PAD_LEN;
>  	u32 segs = netdev->xdp_zc_max_segs;
> +	u8 umem_flags = pool->umem->flags;
>  	bool mbuf = flags & XDP_USE_SG;
>  	bool force_zc, force_copy;
>  	struct netdev_bpf bpf;
> @@ -268,6 +269,7 @@ int xp_assign_dev(struct xsk_buff_pool *pool,
>  	if (!force_zc)
>  		err = 0; /* fallback to copy mode */
>  	if (err) {
> +		pool->umem->flags = umem_flags;
>  		xsk_clear_pool_at_qid(netdev, queue_id);
>  		hlist_del(&pool->dev_node);
>  		pool->netdev = NULL;
> 
> -- 
> 2.56.GIT
> 
> 

      reply	other threads:[~2026-10-22  8:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 22:47 Paul Moses
2026-10-22  8:34 ` 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=atnKf5dNv0Vk1sCo@boxer \
    --to=maciej.fijalkowski@intel.com \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus.karlsson@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=p@1g4.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=stable@vger.kernel.org \
    /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®