Netdev List
 help / color / mirror / Atom feed
From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Matt Fleming <matt@readmodwrite.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Andrew Lunn" <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	"Jesper Dangaard Brouer" <hawk@kernel.org>,
	"John Fastabend" <john.fastabend@gmail.com>,
	"Stanislav Fomichev" <sdf@fomichev.me>,
	"Lorenzo Bianconi" <lorenzo@kernel.org>,
	bpf@vger.kernel.org, netdev@vger.kernel.org,
	stable@vger.kernel.org, kernel-team@cloudflare.com,
	"Matt Fleming" <mfleming@cloudflare.com>
Subject: Re: [PATCH bpf] veth: convert frag_list skbs before running XDP
Date: Tue, 21 Jul 2026 12:58:59 +0200	[thread overview]
Message-ID: <al9Q8yPOfQIVxvp1@boxer> (raw)
In-Reply-To: <al3oXdjTYM_PziJp@matt-Precision-5490>

On Mon, Jul 20, 2026 at 11:24:47AM +0100, Matt Fleming wrote:
> On Fri, Jul 17, 2026 at 11:56:41AM +0200, Toke Høiland-Jørgensen wrote:
> > Matt Fleming <matt@readmodwrite.com> writes:
> > 
> > > diff --git a/drivers/net/veth.c b/drivers/net/veth.c
> > > index 1c5142149175..efb24aae1f26 100644
> > > --- a/drivers/net/veth.c
> > > +++ b/drivers/net/veth.c
> > > @@ -756,7 +756,7 @@ static int veth_convert_skb_to_xdp_buff(struct veth_rq *rq,
> > >  	u32 frame_sz;
> > >  
> > >  	if (skb_shared(skb) || skb_head_is_locked(skb) ||
> > > -	    skb_shinfo(skb)->nr_frags ||
> > > +	    skb_shinfo(skb)->nr_frags || skb_has_frag_list(skb) ||
> > 
> > Isn't 'skb_shinfo(skb)->nr_frags || skb_has_frag_list(skb)' basically
> > the same as 'skb_is_nonlinear(skb)'? Which, incidentally, is what
> > generic XDP uses in the check that guards calling into the
> > skb_pp_cow_data() path.
>  
> Yeah, you're right. I tested that expression and it still fixes the
> bug. I'll update v2 to use skb_is_nonlinear().
> 
> > Looking at those two places, generic XDP checks for 'skb_cloned(skb)',
> > while veth checks 'skb_shared(skb) || skb_head_is_locked(skb)'. AFAICT,
> > the latter is stricter; should we update the generic XDP check?
>  
> Possibly, but the surrounding code isn't set up to deal with
> skb_shared() SKBs so that'd be a larger change. I can take a look at
> that too but I'm going to need more time to get my head around making
> that change correctly given that there's different fallback rules than
> veth.

Hi all,

I had an RFC that made veth to reuse generic XDP code path [0]. Jakub
commented we could have a common pp cow check on both sides. My plan is to
revive this work as this still causes page_pool issues when AF_XDP is used
on veth.

[0]: https://lore.kernel.org/bpf/20260509084858.773921-1-maciej.fijalkowski@intel.com/

Thanks,
Maciej

> 
> > >  	    skb_headroom(skb) < XDP_PACKET_HEADROOM) {
> > >  		if (skb_pp_cow_data(rq->page_pool, pskb, XDP_PACKET_HEADROOM))
> > >  			goto drop;
> > > @@ -771,7 +771,7 @@ static int veth_convert_skb_to_xdp_buff(struct veth_rq *rq,
> > >  	xdp_prepare_buff(xdp, skb->head, skb_headroom(skb),
> > >  			 skb_headlen(skb), true);
> > >  
> > > -	if (skb_is_nonlinear(skb)) {
> > > +	if (skb_shinfo(skb)->nr_frags) {
> > >  		skb_shinfo(skb)->xdp_frags_size = skb->data_len;
> > >  		xdp_buff_set_frags_flag(xdp);
> > >  	} else {
> > > diff --git a/net/core/skbuff.c b/net/core/skbuff.c
> > > index 18dabb4e9cfa..1e837d01a908 100644
> > > --- a/net/core/skbuff.c
> > > +++ b/net/core/skbuff.c
> > > @@ -936,12 +936,11 @@ int skb_pp_cow_data(struct page_pool *pool, struct sk_buff **pskb,
> > >  	int err, i, head_off;
> > >  	void *data;
> > >  
> > > -	/* XDP does not support fraglist so we need to linearize
> > > -	 * the skb.
> > > +	/*
> > > +	 * skb_copy_bits() handles both frags[] and frag_list input. If the
> > > +	 * copied skb remains non-linear, it uses frags[], which is the
> > > +	 * representation used by XDP multi-buffer.
> > >  	 */
> > 
> > This comment sorta reads like a function documentation comment, but it
> > ends up sitting weirdly in the middle of the function body. The comment
> > you're replacing was tied to the statement below, but this one isn't,
> > really. Should we turn it into an actual function doc comment instead?
> 
> Good point. I'll make this a function doc comment.
> 
> Thanks,
> Matt
> 

  reply	other threads:[~2026-07-21 10:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16 10:06 [PATCH bpf] veth: convert frag_list skbs before running XDP Matt Fleming
2026-07-17  9:56 ` Toke Høiland-Jørgensen
2026-07-20 10:24   ` Matt Fleming
2026-07-21 10:58     ` Maciej Fijalkowski [this message]
2026-07-21 13:02       ` Matt Fleming

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=al9Q8yPOfQIVxvp1@boxer \
    --to=maciej.fijalkowski@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kernel-team@cloudflare.com \
    --cc=kuba@kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=matt@readmodwrite.com \
    --cc=mfleming@cloudflare.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=stable@vger.kernel.org \
    --cc=toke@toke.dk \
    /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