Linux io-uring development
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring <io-uring@vger.kernel.org>
Cc: chase xd <sl1589472800@gmail.com>
Subject: Re: [PATCH 1/1] io_uring/rw: forbid multishot async reads
Date: Mon, 17 Feb 2025 13:49:13 +0000	[thread overview]
Message-ID: <1004a92d-bf55-4313-9ec9-c55f8a1dc29f@gmail.com> (raw)
In-Reply-To: <49f065f7b88b7a67190ce65919e7c93c04b3a74b.1739799395.git.asml.silence@gmail.com>

On 2/17/25 13:37, Pavel Begunkov wrote:
> At the moment we can't sanely handle queuing an async request from a
> multishot context, so disable them. It shouldn't matter as pollable
> files / socekts don't normally do async.

I forgot:

Reported-by: chase xd <sl1589472800@gmail.com>

> 
> Cc: stable@vger.kernel.org
> Fixes: fc68fcda04910 ("io_uring/rw: add support for IORING_OP_READ_MULTISHOT")
> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
> ---
>   io_uring/rw.c | 13 +++++++++++--
>   1 file changed, 11 insertions(+), 2 deletions(-)
> 
> diff --git a/io_uring/rw.c b/io_uring/rw.c
> index 96b42c331267..4bda46c5eb20 100644
> --- a/io_uring/rw.c
> +++ b/io_uring/rw.c
> @@ -878,7 +878,15 @@ static int __io_read(struct io_kiocb *req, unsigned int issue_flags)
>   	if (unlikely(ret))
>   		return ret;
>   
> -	ret = io_iter_do_read(rw, &io->iter);
> +	if (unlikely(req->opcode == IORING_OP_READ_MULTISHOT)) {
> +		void *cb_copy = rw->kiocb.ki_complete;
> +
> +		rw->kiocb.ki_complete = NULL;
> +		ret = io_iter_do_read(rw, &io->iter);
> +		rw->kiocb.ki_complete = cb_copy;
> +	} else {
> +		ret = io_iter_do_read(rw, &io->iter);
> +	}
>   
>   	/*
>   	 * Some file systems like to return -EOPNOTSUPP for an IOCB_NOWAIT
> @@ -902,7 +910,8 @@ static int __io_read(struct io_kiocb *req, unsigned int issue_flags)
>   	} else if (ret == -EIOCBQUEUED) {
>   		return IOU_ISSUE_SKIP_COMPLETE;
>   	} else if (ret == req->cqe.res || ret <= 0 || !force_nonblock ||
> -		   (req->flags & REQ_F_NOWAIT) || !need_complete_io(req)) {
> +		   (req->flags & REQ_F_NOWAIT) || !need_complete_io(req) ||
> +		   (issue_flags & IO_URING_F_MULTISHOT)) {
>   		/* read all, failed, already did sync or don't want to retry */
>   		goto done;
>   	}

-- 
Pavel Begunkov


  reply	other threads:[~2025-02-17 13:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 13:37 [PATCH 1/1] io_uring/rw: forbid multishot async reads Pavel Begunkov
2025-02-17 13:49 ` Pavel Begunkov [this message]
2025-02-17 13:58 ` Jens Axboe
2025-02-17 14:03   ` Pavel Begunkov
2025-02-17 14:04     ` Pavel Begunkov
2025-02-17 14:08   ` Pavel Begunkov
2025-02-17 15:37     ` Jens Axboe
2025-02-19  1:35       ` Pavel Begunkov
2025-02-17 14:12   ` Pavel Begunkov
2025-02-17 15:06     ` Jens Axboe
2025-02-17 15:33       ` Pavel Begunkov
2025-02-17 15:57         ` Jens Axboe
2025-02-17 17:51           ` Pavel Begunkov

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=1004a92d-bf55-4313-9ec9-c55f8a1dc29f@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=io-uring@vger.kernel.org \
    --cc=sl1589472800@gmail.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