From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <bjorn@kernel.org>,
<magnus.karlsson@intel.com>, <jonathan.lemon@gmail.com>,
<sdf@fomichev.me>, <ast@kernel.org>, <daniel@iogearbox.net>,
<hawk@kernel.org>, <john.fastabend@gmail.com>, <horms@kernel.org>,
<andrew+netdev@lunn.ch>, <bpf@vger.kernel.org>,
<netdev@vger.kernel.org>, Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net v4 0/5] xsk: fix meta and publish of cq issues
Date: Thu, 21 May 2026 14:59:54 +0200 [thread overview]
Message-ID: <ag8ByhbrNNJaESYi@boxer> (raw)
In-Reply-To: <CAL+tcoAJ3i-WGnVx-9ASF29gPNAaP2ucw76x3ftLog-b1TPf_w@mail.gmail.com>
On Thu, May 21, 2026 at 08:41:08PM +0800, Jason Xing wrote:
> On Thu, May 21, 2026 at 8:24 PM Maciej Fijalkowski
> <maciej.fijalkowski@intel.com> wrote:
> >
> > On Wed, May 20, 2026 at 08:42:39AM +0800, Jason Xing wrote:
> > > From: Jason Xing <kernelxing@tencent.com>
> > >
> > > The series is the product of previous review from sashiko[1].
> > >
> > > 1) META
> > > patch 1: address TOCTOU around metadata.
> > >
> > > 2) PUBLISH of CQ
> > > patch 2: make sure xsk_addr->addrs[] can be published to cq when
> > > overflow occurs.
> > > patch 3: keep cleaning up the continuation descs (more than 17) and
> > > publish its address when overflow occurs.
> > > patch 4: like patch 3, but only handles the invalid descs cases.
> > >
> > > [1]: https://lore.kernel.org/all/20260502200722.53960-1-kerneljasonxing@gmail.com/
> > >
> > > ---
> > > V4
> > > Link: https://lore.kernel.org/all/20260517063311.28921-1-kerneljasonxing@gmail.com/
> > > 1. correct the description of xmit path in patch 3 (sashiko)
> > > 2. move set logic into xmit path in patch 3 (Stan)
> > >
> > > V3
> > > Link: https://lore.kernel.org/all/20260515123018.80147-1-kerneljasonxing@gmail.com/
> > > 1. avoid breaking previous usage of sendto, and siliently handle
> > > overflow case (Stan, sashiko)
> > > 2. add one particular exception process in patch 4 (sashiko)
> > > 3. adjust the selftest to make sure it passes in either virutal or
> > > physical machines, which includes add usleep to support physical machine.
> > >
> > > V2
> > > Link: https://lore.kernel.org/all/20260510012310.88570-1-kerneljasonxing@gmail.com/
> > > 1. adjust selftests (Jakub)
> > > 2. add READ_ONCE in patch 1 (Stan)
> >
> > FWIW I still get test failures (yes with patch 5 applied). PTAL.
>
> Thanks for the test. But I've tried with ixgbe driver...
>
> I noticed there are some flaky tests which have nothing to do with the
> series. Can you confirm that it's not caused because of the series?
That explains the different results as i am using i40e/ice which have
multi-buffer support whereas ixgbe does not even support mbuf at XDP.
Broken tests are from mbuf cases.
>
> Thanks,
> Jason
>
>
> >
> > >
> > >
> > > Jason Xing (5):
> > > xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata()
> > > xsk: fix buffer leak in xsk_drop_skb() for AF_XDP multi-buffer Tx
> > > xsk: drain continuation descs after overflow in xsk_build_skb()
> > > xsk: drain continuation descs on invalid descriptor in
> > > __xsk_generic_xmit()
> > > selftests/xsk: drain CQ to wait for TX completion
> > >
> > > include/net/xdp_sock.h | 1 +
> > > net/xdp/xsk.c | 44 +++++++++++++----
> > > .../selftests/bpf/prog_tests/test_xsk.c | 48 +++++++++++--------
> > > 3 files changed, 63 insertions(+), 30 deletions(-)
> > >
> > > --
> > > 2.43.7
> > >
next prev parent reply other threads:[~2026-05-21 13:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 0:42 [PATCH net v4 0/5] xsk: fix meta and publish of cq issues Jason Xing
2026-05-20 0:42 ` [PATCH net v4 1/5] xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata() Jason Xing
2026-05-21 12:04 ` Maciej Fijalkowski
2026-05-20 0:42 ` [PATCH net v4 2/5] xsk: fix buffer leak in xsk_drop_skb() for AF_XDP multi-buffer Tx Jason Xing
2026-05-21 12:05 ` Maciej Fijalkowski
2026-05-20 0:42 ` [PATCH net v4 3/5] xsk: drain continuation descs after overflow in xsk_build_skb() Jason Xing
2026-05-20 16:10 ` Maciej Fijalkowski
2026-05-20 23:53 ` Jason Xing
2026-05-21 12:02 ` Maciej Fijalkowski
2026-05-21 13:10 ` Jason Xing
2026-05-22 9:06 ` Magnus Karlsson
2026-05-22 9:22 ` Jason Xing
2026-05-20 0:42 ` [PATCH net v4 4/5] xsk: drain continuation descs on invalid descriptor in __xsk_generic_xmit() Jason Xing
2026-05-20 0:42 ` [PATCH net v4 5/5] selftests/xsk: drain CQ to wait for TX completion Jason Xing
2026-05-21 12:23 ` [PATCH net v4 0/5] xsk: fix meta and publish of cq issues Maciej Fijalkowski
2026-05-21 12:41 ` Jason Xing
2026-05-21 12:59 ` Maciej Fijalkowski [this message]
2026-05-21 13:07 ` Jason Xing
2026-05-21 14:24 ` Maciej Fijalkowski
2026-05-22 8:55 ` Jason Xing
2026-05-22 13:48 ` Jason Xing
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=ag8ByhbrNNJaESYi@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bjorn@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=jonathan.lemon@gmail.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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