From: Jeff Layton <jlayton@kernel.org>
To: "Luís Henriques" <lhenriques@suse.de>,
"Xiubo Li" <xiubli@redhat.com>,
"Ilya Dryomov" <idryomov@gmail.com>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ceph: invalidate pages when doing direct/sync writes
Date: Thu, 07 Apr 2022 10:42:57 -0400 [thread overview]
Message-ID: <96a44a4224b67b9ec36198bc0586064df5c4ad2a.camel@kernel.org> (raw)
In-Reply-To: <20220407143834.7516-1-lhenriques@suse.de>
On Thu, 2022-04-07 at 15:38 +0100, Luís Henriques wrote:
> When doing a direct/sync write, we need to invalidate the page cache in
> the range being written to. If we don't do this, the cache will include
> invalid data as we just did a write that avoided the page cache.
>
> Signed-off-by: Luís Henriques <lhenriques@suse.de>
> ---
> fs/ceph/file.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> Ok, here's a new attempt. After discussion in this thread and on IRC, I
> think this is the right fix. generic/647 now passes with and without
> encryption. Thanks!
>
> Changes since v2:
> - Invalidation needs to be done after a write
>
> Changes since v1:
> - Replaced truncate_inode_pages_range() by invalidate_inode_pages2_range
> - Call fscache_invalidate with FSCACHE_INVAL_DIO_WRITE if we're doing DIO
>
> diff --git a/fs/ceph/file.c b/fs/ceph/file.c
> index 5072570c2203..63e67eb60310 100644
> --- a/fs/ceph/file.c
> +++ b/fs/ceph/file.c
> @@ -1938,6 +1938,15 @@ ceph_sync_write(struct kiocb *iocb, struct iov_iter *from, loff_t pos,
> break;
> }
> ceph_clear_error_write(ci);
> + ret = invalidate_inode_pages2_range(
> + inode->i_mapping,
> + pos >> PAGE_SHIFT,
> + (pos + len - 1) >> PAGE_SHIFT);
> + if (ret < 0) {
> + dout("invalidate_inode_pages2_range returned %d\n",
> + ret);
> + ret = 0;
> + }
> pos += len;
> written += len;
> dout("sync_write written %d\n", written);
Looks good. I suspect we can also remove the
invalidate_indode_pages2_range call earlier in this function too. I may
roll that into this patch.
I'll give this an xfstests run with fscrypt enabled and see how it does.
Thanks!
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2022-04-07 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 14:38 [PATCH v3] ceph: invalidate pages when doing direct/sync writes Luís Henriques
2022-04-07 14:42 ` Jeff Layton [this message]
2022-04-07 15:03 ` Luís Henriques
2022-04-07 14:48 ` Xiubo Li
2022-04-07 15:05 ` Luís Henriques
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=96a44a4224b67b9ec36198bc0586064df5c4ad2a.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=lhenriques@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xiubli@redhat.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