From: Jens Axboe <axboe@kernel.dk>
To: "Lukáš Lalinský" <lukas@lalinsky.com>
Cc: io-uring@vger.kernel.org
Subject: Re: io_uring: SENDMSG/WRITEV return -EAGAIN on O_NONBLOCK socket after peer half-close
Date: Fri, 6 Nov 2026 16:54:12 -0700 [thread overview]
Message-ID: <cedaa253-48b6-46da-a142-c1d4fc3f6f29@kernel.dk> (raw)
In-Reply-To: <7526dc5c-fbc1-4b26-96a1-f416d5bb4106@app.fastmail.com>
On 11/6/26 5:04 AM, Lukáš Lalinský wrote:
> On Tue, Nov 3, 2026, at 5:00 PM, Jens Axboe wrote:
>> Can you try with this on top?
>
> Hi Jens,
>
> I tested the three patches together on current master. Everything I
> know of is fixed:
>
> - After the peer's half-close, a waiting SEND, SENDMSG or WRITEV keeps
> waiting and completes normally once the peer reads, with or without
> O_NONBLOCK.
> - The same now holds when the peer has sent urgent data that the
> application doesn't read.
> - A RECVMSG that is woken repeatedly without data no longer completes
> with -EAGAIN.
> - The cancel now finds the send, both after a half-close and with
> unread urgent data, and the send completes with -ECANCELED.
>
> Our runtime's test suite also passes on the patched kernel.
Great! Patch 1+3 are in Linus's tree now, and I sent out the net
patch as well to netdev just now. Hopefully all will land in
7.4, and I will ensure they all go to stable as well.
--
Jens Axboe
prev parent reply other threads:[~2026-11-06 23:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 18:54 io_uring: SENDMSG/WRITEV return -EAGAIN on O_NONBLOCK socket after peer half-close Lukáš Lalinský
2026-10-29 19:48 ` Jens Axboe
2026-10-29 20:42 ` Lukáš Lalinský
[not found] ` <5475728c-6cd9-4d61-bcee-5c8a42f1951d@app.fastmail.com>
2026-11-03 16:00 ` Jens Axboe
2026-11-06 12:04 ` Lukáš Lalinský
2026-11-06 23:54 ` Jens Axboe [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=cedaa253-48b6-46da-a142-c1d4fc3f6f29@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=lukas@lalinsky.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