From: Alex Markuze <amarkuze@redhat.com>
To: netdev-bot+sinfo@kernel.org
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH net-next 0/4] net: streamline skb_splice_from_iter()
Date: Mon, 16 Nov 2026 07:57:16 +0000 [thread overview]
Message-ID: <179481582370.4133712.12198402768754157869.netdev-splice-background@redhat.com> (raw)
In-Reply-To: <179430999926.488859.4270273148397539600@kernel.org>
Hi,
The issues in patch 1 were found during development and testing of
opaque TCP payload objects [1], not from a production report.
Both were reproduced in added in-kernel helper tests using the generic
extraction path:
- With a nonempty iterator, maxsize == 0 returned -EIO instead of 0.
- Deliberately supplying slab-backed memory caused sendpage_ok() to
reject the page, but the iterator remained advanced over unappended
bytes, both with and without an accepted prefix.
[1] https://lore.kernel.org/io-uring/20261110132006.3280986-1-amarkuze@redhat.com/
Thanks,
Alex
prev parent reply other threads:[~2026-11-16 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 11:23 Alex Markuze
2026-11-10 11:23 ` [RFC PATCH net-next 1/4] net: preserve splice iterator progress on rejection Alex Markuze
2026-11-10 11:23 ` [RFC PATCH net-next 2/4] net: skb_splice_from_iter(): group consecutive pages of a folio Alex Markuze
2026-11-10 11:23 ` [RFC PATCH net-next 3/4] net: skb_splice_from_iter(): walk ITER_BVEC segments directly Alex Markuze
2026-11-10 11:23 ` [RFC PATCH net-next 4/4] net: add basic splice KUnit tests Alex Markuze
2026-11-10 11:26 ` [RFC PATCH net-next 0/4] net: streamline skb_splice_from_iter() netdev-bot+sinfo
2026-11-16 7:57 ` Alex Markuze [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=179481582370.4133712.12198402768754157869.netdev-splice-background@redhat.com \
--to=amarkuze@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sinfo@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
all inboxes | Powered by JetHome®