From: Dave Chinner <david@fromorbit.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fs: RWF_NOWAIT should imply IOCB_NOIO
Date: Tue, 11 Aug 2020 16:13:14 +1000 [thread overview]
Message-ID: <20200811061314.GF2079@dread.disaster.area> (raw)
In-Reply-To: <e8325bef-7e91-5fd4-fa25-74cfa169ffd2@kernel.dk>
On Mon, Aug 10, 2020 at 06:48:19PM -0600, Jens Axboe wrote:
> With the change allowing read-ahead for IOCB_NOWAIT, we changed the
> RWF_NOWAIT semantics of only doing cached reads. Since we know have
> IOCB_NOIO to manage that specific side of it, just make RWF_NOWAIT
> imply IOCB_NOIO as well to restore the previous behavior.
>
> Fixes: 2e85abf053b9 ("mm: allow read-ahead with IOCB_NOWAIT set")
> Reported-by: Dave Chinner <david@fromorbit.com>
> Signed-off-by: Jens Axboe <axboe@kernel.dk>
>
> ---
>
> This was a known change with the buffered async read change, but we
> didn't have IOCB_NOIO until late in 5.8. Now that bases are synced,
> make the change to make RWF_NOWAIT behave like past kernels.
>
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index bd7ec3eaeed0..f1cca4bfdd7b 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -3293,7 +3293,7 @@ static inline int kiocb_set_rw_flags(struct kiocb *ki, rwf_t flags)
> if (flags & RWF_NOWAIT) {
> if (!(ki->ki_filp->f_mode & FMODE_NOWAIT))
> return -EOPNOTSUPP;
> - kiocb_flags |= IOCB_NOWAIT;
> + kiocb_flags |= IOCB_NOWAIT | IOCB_NOIO;
> }
> if (flags & RWF_HIPRI)
> kiocb_flags |= IOCB_HIPRI;
Looks good.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2020-08-11 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 0:48 [PATCH] fs: RWF_NOWAIT should imply IOCB_NOIO Jens Axboe
2020-08-11 6:13 ` Dave Chinner [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 \
--in-reply-to=20200811061314.GF2079@dread.disaster.area \
--to=david@fromorbit.com \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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