From: Jens Axboe <[email protected]>
To: Hrvoje Zeba <[email protected]>, [email protected]
Subject: Re: recvmsg not honoring O_NONBLOCK
Date: Sat, 9 Jul 2022 09:25:58 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAEsUgYg5zx5Zk_wp9=YXf5Y+qPh9vx7adDN=B_rpa3zoh2YSew@mail.gmail.com>
On 7/9/22 8:21 AM, Hrvoje Zeba wrote:
> Hi folks,
>
> I was adapting msquic library to work with iouring and found an issue
> with recvmsg() where it ignores O_NONBLOCK flag set on the file
> descriptor. If MSG_DONTWAIT is set in flags, it behaves as expected.
> I've attached a simple test which currently just hangs on iouring's
> recvmsg(). I'm guessing sendmsg() behaves the same way but I have no
> idea how to fill the buffer to reliably test it.
I am guessing that you're waiting off waiting for the event. It's not
stalled on the issue, it'll arm poll and wait for an event. I won't go
into too much of a ran on O_NONBLOCK, but it's a giant mess, and where
possible, io_uring relies on per-request non-block flags as that is much
saner behavior.
--
Jens Axboe
next prev parent reply other threads:[~2022-07-09 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 14:21 recvmsg not honoring O_NONBLOCK Hrvoje Zeba
2022-07-09 15:25 ` Jens Axboe [this message]
2022-07-09 16:46 ` Hrvoje Zeba
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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