From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/2] Fix bugs in tcp_splice_sock_handler()
Date: Wed, 9 Apr 2025 16:35:39 +1000 [thread overview]
Message-ID: <20250409063541.1411177-1-david@gibson.dropbear.id.au> (raw)
Patch 1/2 here fixes what I think is the bug causing the latest issue
in:
https://github.com/containers/podman/issues/23686
While fixing that I spotted the bug fixed in 2/2. Definitely a bug,
although I suspect we'll mostly get away with it if the --trace option
is not enabled.
David Gibson (2):
tcp_splice: Don't double could bytes read on EINTR
tcp_splice: Don't clobber errno before checking for EAGAIN
tcp_splice.c | 43 ++++++++++++++++++++++---------------------
1 file changed, 22 insertions(+), 21 deletions(-)
--
2.49.0
next reply other threads:[~2025-04-09 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 6:35 David Gibson [this message]
2025-04-09 6:35 ` [PATCH 1/2] tcp_splice: Don't double could bytes read on EINTR David Gibson
2025-04-09 6:35 ` [PATCH 2/2] tcp_splice: Don't clobber errno before checking for EAGAIN David Gibson
2025-04-09 22:41 ` [PATCH 0/2] Fix bugs in tcp_splice_sock_handler() Stefano Brivio
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=20250409063541.1411177-1-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).