CEPH filesystem development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: xiubli@redhat.com
Cc: idryomov@gmail.com, vshankar@redhat.com, ceph-devel@vger.kernel.org
Subject: Re: [RFC PATCH] ceph: no need to invalidate the fscache twice
Date: Thu, 07 Apr 2022 06:24:04 -0400	[thread overview]
Message-ID: <39a5a060f9be3bd9e7e25db29f925a275930bf64.camel@kernel.org> (raw)
In-Reply-To: <20220407051242.692846-1-xiubli@redhat.com>

On Thu, 2022-04-07 at 13:12 +0800, xiubli@redhat.com wrote:
> From: Xiubo Li <xiubli@redhat.com>
> 
> [ Introduced by commit 400e1286c0ec3: "ceph: conversion to new fscache API" ]
> 
> Signed-off-by: Xiubo Li <xiubli@redhat.com>
> ---
> 
> Jeff, is there any reason we need to invalidate the fscache twice in
> ceph_do_invalidate_pages() ?
> 

No, that was a mistake. I'll go ahead and fold this patch into
400e1286c0ec3.

> 
>  fs/ceph/inode.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/fs/ceph/inode.c b/fs/ceph/inode.c
> index cc1829ab497d..b721d86fb582 100644
> --- a/fs/ceph/inode.c
> +++ b/fs/ceph/inode.c
> @@ -2084,7 +2084,6 @@ static void ceph_do_invalidate_pages(struct inode *inode)
>  	orig_gen = ci->i_rdcache_gen;
>  	spin_unlock(&ci->i_ceph_lock);
>  
> -	ceph_fscache_invalidate(inode, false);
>  	if (invalidate_inode_pages2(inode->i_mapping) < 0) {
>  		pr_err("invalidate_inode_pages2 %llx.%llx failed\n",
>  		       ceph_vinop(inode));

Thanks!
-- 
Jeff Layton <jlayton@kernel.org>

      reply	other threads:[~2022-04-07 10:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  5:12 [RFC PATCH] ceph: no need to invalidate the fscache twice xiubli
2022-04-07 10:24 ` Jeff Layton [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=39a5a060f9be3bd9e7e25db29f925a275930bf64.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.com \
    --cc=vshankar@redhat.com \
    --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