public inbox for [email protected]
 help / color / mirror / Atom feed
From: Norman Maurer <[email protected]>
To: [email protected]
Cc: Josef <[email protected]>
Subject: IORING_OP_READ and O_NONBLOCK behaviour
Date: Wed, 2 Sep 2020 12:09:29 +0200	[thread overview]
Message-ID: <[email protected]> (raw)

Hi there,

We are currently working on integrating io_uring into netty and found some “suprising” behaviour which seems like a bug to me.

When a socket is marked as non blocking (accepted with O_NONBLOCK flag set) and there is no data to be read IORING_OP_READ should complete directly with EAGAIN or EWOULDBLOCK. This is not the case and it basically blocks forever until there is some data to read. Is this expected ?

This seems to be somehow related to a bug that was fixed for IO_URING_ACCEPT with non blocking sockets:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.8&id=e697deed834de15d2322d0619d51893022c90ea2

Thanks
Norman


             reply	other threads:[~2020-09-02 10:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 10:09 Norman Maurer [this message]
2020-09-02 14:45 ` IORING_OP_READ and O_NONBLOCK behaviour Jens Axboe
2020-09-02 15:26   ` Pavel Begunkov
2020-09-02 15:35     ` Jens Axboe
2020-09-02 16:00       ` Pavel Begunkov
2020-09-02 16:02         ` Pavel Begunkov
2020-09-02 16:05         ` Jens Axboe

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=28EF4A51-2B6D-4857-A9E8-2E28E530EFA6@googlemail.com \
    [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