From: Amir Goldstein <amir73il@gmail.com>
To: Reuben Hawkins <reubenhwk@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, mszeredi@redhat.com,
willy@infradead.org, viro@zeniv.linux.org.uk, brauner@kernel.org
Subject: Re: [PATCH v2] vfs: fix readahead(2) on block devices
Date: Mon, 11 Sep 2023 16:23:51 +0300 [thread overview]
Message-ID: <CAOQ4uxizQDAMUX--tJkGG8CF38adj3QRqHcsXo6yU20yREBABQ@mail.gmail.com> (raw)
In-Reply-To: <20230911114713.25625-1-reubenhwk@gmail.com>
On Mon, Sep 11, 2023 at 2:49 PM Reuben Hawkins <reubenhwk@gmail.com> wrote:
>
> Readahead was factored to call generic_fadvise. That refactor added an
> S_ISREG restriction which broke readahead on block devices.
>
> This change removes the S_ISREG restriction to fix block device readahead.
> The change also means that readahead will return -ESPIPE on FIFO files
> instead of -EINVAL.
>
> Fixes: 3d8f7615319b ("vfs: implement readahead(2) using POSIX_FADV_WILLNEED")
> Signed-off-by: Reuben Hawkins <reubenhwk@gmail.com>
> ---
Reviewed-by: Amir Goldstein <amir73il@gmail.com>
Christian,
I suggest adding the link to the original bug report on commit:
Closes: https://lore.kernel.org/linux-fsdevel/CAOQ4uxhE8En64rr3mx1UAOqqzb3A-GoeR7cx2D+V73ytr6YLjw@mail.gmail.com/
Thanks,
Amir.
> mm/readahead.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/mm/readahead.c b/mm/readahead.c
> index e815c114de21..ef3b23a41973 100644
> --- a/mm/readahead.c
> +++ b/mm/readahead.c
> @@ -734,8 +734,7 @@ ssize_t ksys_readahead(int fd, loff_t offset, size_t count)
> * on this file, then we must return -EINVAL.
> */
> ret = -EINVAL;
> - if (!f.file->f_mapping || !f.file->f_mapping->a_ops ||
> - !S_ISREG(file_inode(f.file)->i_mode))
> + if (!f.file->f_mapping || !f.file->f_mapping->a_ops)
> goto out;
>
> ret = vfs_fadvise(f.file, offset, count, POSIX_FADV_WILLNEED);
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-09-11 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 11:47 [PATCH v2] vfs: fix readahead(2) on block devices Reuben Hawkins
2023-09-11 13:23 ` Amir Goldstein [this message]
2023-09-11 13:51 ` Christian Brauner
2023-09-14 8:35 ` Jan Kara
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=CAOQ4uxizQDAMUX--tJkGG8CF38adj3QRqHcsXo6yU20yREBABQ@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=reubenhwk@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).