From: Bruno Xavier <bfxavier@gmail.com>
To: fabriciogava@gmail.com, florian@schauer.to
Cc: netdev@vger.kernel.org, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, davem@davemloft.net, lorenzo@kernel.org,
hawk@kernel.org, ilias.apalodimas@linaro.org,
bpf@vger.kernel.org, Bruno Xavier <bfxavier@gmail.com>
Subject: Re: [PATCH] net: skbuff: keep the page_pool fragment offset aligned in skb_pp_cow_data()
Date: Mon, 31 Aug 2026 00:11:13 +0200 [thread overview]
Message-ID: <20260830221113.1238112-1-bfxavier@gmail.com> (raw)
In-Reply-To: <20260830212331.546227-1-fabriciogava@gmail.com>
On Sun, Aug 30, 2026 at 09:23:27PM +0000, Fabricio Gava wrote:
> That version has already been sent, by Florian Schauer, the day before
> this patch -- "page_pool: keep frag_offset aligned for odd-sized requests",
> now at v2:
Thanks for linking the threads, I had not seen Florian's v1.
> xdp_copy_frags_from_zc() does the same, net/core/xdp.c:700-705:
I mispoke in my own notes on this one. I checked system_page_pool for
other consumers before sending and read it as having exactly one,
net/core/dev.c:5619. xdp.c:753 is the second. So fixing skb_pp_cow_data()
alone leaves the defect reachable through the zero-copy path.
Florian's patch is the right fix. Please drop this one.
On veth, drivers/net/veth.c:762 passes its own rq->page_pool rather than
the per-cpu one, so I don't think it widens the sharing. It widens where
the misaligning loop runs, which is the part your reading of the Fixes tag
gets at.
I have the reproducer and an A/B kernel harness here. Building v2 now,
numbers on Florian's thread.
Thanks,
Bruno
prev parent reply other threads:[~2026-08-30 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 12:29 [PATCH] net: skbuff: keep the page_pool fragment offset aligned in skb_pp_cow_data() Bruno Xavier
2026-08-30 21:23 ` Fabricio Gava
2026-08-30 22:11 ` Bruno Xavier [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=20260830221113.1238112-1-bfxavier@gmail.com \
--to=bfxavier@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fabriciogava@gmail.com \
--cc=florian@schauer.to \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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