From: Vasily Averin <vvs@virtuozzo.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH] fuse: cleanup fuse_wait_on_page_writeback
Date: Mon, 22 Jul 2019 10:18:39 +0300 [thread overview]
Message-ID: <d8ebd68d-684b-ab32-fcc9-2eaaf894c252@virtuozzo.com> (raw)
In-Reply-To: <64e2db3a-cf58-0158-e097-1a504a8bb496@virtuozzo.com>
I forget to add this patch was used in OpenVZ kernels last few years.
On 7/22/19 10:17 AM, Vasily Averin wrote:
> From: Maxim Patlasov <mpatlasov@virtuozzo.com>
> fuse_wait_on_page_writeback() always returns zero and nobody cares.
> Let's make it void.
>
> Signed-off-by: Maxim Patlasov <mpatlasov@virtuozzo.com>
> Signed-off-by: Vasily Averin <vvs@virtuozzo.com>
> ---
> fs/fuse/file.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/fs/fuse/file.c b/fs/fuse/file.c
> index 5ae2828beb00..e076c2cf65b0 100644
> --- a/fs/fuse/file.c
> +++ b/fs/fuse/file.c
> @@ -383,12 +383,11 @@ static inline bool fuse_page_is_writeback(struct inode *inode, pgoff_t index)
> * Since fuse doesn't rely on the VM writeback tracking, this has to
> * use some other means.
> */
> -static int fuse_wait_on_page_writeback(struct inode *inode, pgoff_t index)
> +static void fuse_wait_on_page_writeback(struct inode *inode, pgoff_t index)
> {
> struct fuse_inode *fi = get_fuse_inode(inode);
>
> wait_event(fi->page_waitq, !fuse_page_is_writeback(inode, index));
> - return 0;
> }
>
> /*
>
next prev parent reply other threads:[~2019-07-22 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 7:17 Vasily Averin
2019-07-22 7:18 ` Vasily Averin [this message]
2019-08-01 11:03 ` Miklos Szeredi
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=d8ebd68d-684b-ab32-fcc9-2eaaf894c252@virtuozzo.com \
--to=vvs@virtuozzo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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
all inboxes | Powered by JetHome®