All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring <io-uring@vger.kernel.org>
Cc: Norman Maurer <norman.maurer@googlemail.com>
Subject: Re: [PATCH] io_uring: no read-retry on -EAGAIN error and O_NONBLOCK marked file
Date: Wed, 2 Sep 2020 19:09:51 +0300	[thread overview]
Message-ID: <cdc949ce-059b-2f4f-bb16-f4e9554eb975@gmail.com> (raw)
In-Reply-To: <5d91a8ea-5748-803a-d2dc-ef21fe27e39e@kernel.dk>

On 02/09/2020 19:00, Jens Axboe wrote:
>     Actually two things that need fixing up here:
>     
>     - The io_rw_reissue() -EAGAIN retry is explicit to block devices and
>       regular files, so don't ever attempt to do that on other types of
>       files.
>     
>     - If we hit -EAGAIN on a nonblock marked file, don't arm poll handler for
>       it. It should just complete with -EAGAIN.
>     
>     Cc: stable@vger.kernel.org
>     Reported-by: Norman Maurer <norman.maurer@googlemail.com>
>     Signed-off-by: Jens Axboe <axboe@kernel.dk>
> 
> ---
> 
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index b1ccd7072d93..65656102bbeb 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -2300,8 +2300,11 @@ static bool io_resubmit_prep(struct io_kiocb *req, int error)
>  static bool io_rw_reissue(struct io_kiocb *req, long res)
>  {
>  #ifdef CONFIG_BLOCK
> +	umode_t mode = file_inode(req->file)->i_mode;
>  	int ret;
>  
> +	if (!S_ISBLK(mode) && !S_ISREG(mode))
> +		return false;
>  	if ((res != -EAGAIN && res != -EOPNOTSUPP) || io_wq_current_is_worker())
>  		return false;
>  
> @@ -3146,6 +3149,9 @@ static int io_read(struct io_kiocb *req, bool force_nonblock,
>  		/* IOPOLL retry should happen for io-wq threads */
>  		if (!force_nonblock && !(req->ctx->flags & IORING_SETUP_IOPOLL))
>  			goto done;
> +		/* no retry on NONBLOCK marked file */
> +		if (req->file->f_flags & O_NONBLOCK)
> +			goto done;

Looks like it works with open(O_NONBLOCK) but not with IOCB_NOWAIT in the
request's flags. Is that so?


>  		/* some cases will consume bytes even on error returns */
>  		iov_iter_revert(iter, iov_count - iov_iter_count(iter));
>  		ret = io_setup_async_rw(req, iovec, inline_vecs, iter, false);
> @@ -3291,8 +3297,12 @@ static int io_write(struct io_kiocb *req, bool force_nonblock,
>  		/* IOPOLL retry should happen for io-wq threads */
>  		if ((req->ctx->flags & IORING_SETUP_IOPOLL) && ret2 == -EAGAIN)
>  			goto copy_iov;
> +done:
>  		kiocb_done(kiocb, ret2, cs);
>  	} else {
> +		/* no retry on NONBLOCK marked file */
> +		if (req->file->f_flags & O_NONBLOCK)
> +			goto done;
>  copy_iov:
>  		/* some cases will consume bytes even on error returns */
>  		iov_iter_revert(iter, iov_count - iov_iter_count(iter));
> 

-- 
Pavel Begunkov

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 16:00 [PATCH] io_uring: no read-retry on -EAGAIN error and O_NONBLOCK marked file Jens Axboe
2020-09-02 16:09 ` Pavel Begunkov [this message]
2020-09-02 16:32   ` 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=cdc949ce-059b-2f4f-bb16-f4e9554eb975@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=norman.maurer@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.