public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: io-uring <[email protected]>
Subject: Re: [PATCH] io_uring: don't attempt to IOPOLL for MSG_RING requests
Date: Tue, 17 May 2022 12:48:00 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 5/17/22 12:34 PM, Jens Axboe wrote:
> We gate whether to IOPOLL for a request on whether the opcode is allowed
> on a ring setup for IOPOLL and if it's got a file assigned. MSG_RING
> is the only one that allows a file yet isn't pollable, it's merely
> supported to allow communication on an IOPOLL ring, not because we can
> poll for completion of it.
> 
> Put the assigned file early and clear it, so we don't attempt to poll
> for it.
> 
> Reported-by: [email protected]
> Fixes: 3f1d52abf098 ("io_uring: defer msg-ring file validity check until command issue")
> Signed-off-by: Jens Axboe <[email protected]>
> 
> ---
> 
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 91de361ea9ab..3cb0bc68d822 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -5007,6 +5007,9 @@ static int io_fadvise(struct io_kiocb *req, unsigned int issue_flags)
>  	if (ret < 0)
>  		req_set_fail(req);
>  	__io_req_complete(req, issue_flags, ret, 0);
> +	/* put file to avoid an attempt to IOPOLL the req */
> +	io_put_file(req->file);
> +	req->file = NULL;
>  	return 0;
>  }

patch unhelpfully applying to the wrong function when ported from
for-next to 5.18. Here's the right one:

commit aa184e8671f0f911fc2fb3f68cd506e4d7838faa
Author: Jens Axboe <[email protected]>
Date:   Tue May 17 12:32:05 2022 -0600

    io_uring: don't attempt to IOPOLL for MSG_RING requests
    
    We gate whether to IOPOLL for a request on whether the opcode is allowed
    on a ring setup for IOPOLL and if it's got a file assigned. MSG_RING
    is the only one that allows a file yet isn't pollable, it's merely
    supported to allow communication on an IOPOLL ring, not because we can
    poll for completion of it.
    
    Put the assigned file early and clear it, so we don't attempt to poll
    for it.
    
    Reported-by: [email protected]
    Fixes: 3f1d52abf098 ("io_uring: defer msg-ring file validity check until command issue")
    Signed-off-by: Jens Axboe <[email protected]>

diff --git a/fs/io_uring.c b/fs/io_uring.c
index 91de361ea9ab..e0823f58f795 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -4481,6 +4481,9 @@ static int io_msg_ring(struct io_kiocb *req, unsigned int issue_flags)
 	if (ret < 0)
 		req_set_fail(req);
 	__io_req_complete(req, issue_flags, ret, 0);
+	/* put file to avoid an attempt to IOPOLL the req */
+	io_put_file(req->file);
+	req->file = NULL;
 	return 0;
 }
 
-- 
Jens Axboe


      reply	other threads:[~2022-05-17 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 18:34 [PATCH] io_uring: don't attempt to IOPOLL for MSG_RING requests Jens Axboe
2022-05-17 18:48 ` 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 \
    [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