mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <slava@dubeyko.com>
To: xiubo.li@clyso.com, Ilya Dryomov <idryomov@gmail.com>,
	Alex Markuze <amarkuze@redhat.com>
Cc: Dhairya Parmar <dparmar@redhat.com>,
	ceph-devel@vger.kernel.org,  linux-kernel@vger.kernel.org,
	Andras Pataki <apataki@flatironinstitute.org>
Subject: Re: [PATCH] ceph: do not cache negative dentries for snapped directories
Date: Thu, 23 Jul 2026 09:52:40 -0700	[thread overview]
Message-ID: <f8be59729e99bfc9182d74eb0fe6f1782dbc1dc8.camel@dubeyko.com> (raw)
In-Reply-To: <20260723-b4-snap-negative-dentry-v1-1-c78178117929@clyso.com>

On Thu, 2026-07-23 at 14:28 +0800, Xiubo Li via B4 Relay wrote:
> From: Xiubo Li <xiubo.li@clyso.com>
> 
> When a LOOKUP/LOOKUPSNAP in a snapped directory returns ENOENT
> without a trace, ceph_finish_lookup() creates a negative dentry
> via d_add(dentry, NULL).  For live directories this is fine — the
> dentry naturally expires.  But for snapped directories,
> ceph_d_revalidate() unconditionally trusts all cached dentries
> (valid = 1), so a negative dentry created by a transient error
> persists forever, hiding entries that genuinely exist in the
> snapshot.
> 
> Only cache negative dentries for live (non-snapshotted) parent
> directories.  For snapped parents, skip the negative dentry so
> that VFS retries the lookup on the next access.  Since the
> conditions that trigger a negative dentry (MDS transient error,
> local ENOENT shortcut, or MDS null dentry lease) are all rare in
> snapped directories, the performance impact of this change is
> negligible.
> 
> Reported-by: Andras Pataki <apataki@flatironinstitute.org>
> Closes: https://tracker.ceph.com/issues/78529
> Signed-off-by: Xiubo Li <xiubo.li@clyso.com>
> ---
>  fs/ceph/dir.c   | 10 ++++++++--
>  fs/ceph/inode.c |  3 ++-
>  2 files changed, 10 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/ceph/dir.c b/fs/ceph/dir.c
> index b4b541a1180c..d5d8f935fb62 100644
> --- a/fs/ceph/dir.c
> +++ b/fs/ceph/dir.c
> @@ -774,8 +774,13 @@ struct dentry *ceph_finish_lookup(struct
> ceph_mds_request *req,
>  				d_drop(dentry);
>  				err = -ENOENT;
>  			} else {
> -				if (d_unhashed(dentry))
> -					d_add(dentry, NULL);
> +				if (d_unhashed(dentry)) {
> +					struct inode *parent =
> +						d_inode(dentry-
> >d_parent);
> +					if (!parent ||
> +					    ceph_snap(parent) ==
> CEPH_NOSNAP)
> +						d_add(dentry, NULL);
> +				}
>  			}
>  		}
>  	}
> @@ -840,6 +845,7 @@ static struct dentry *ceph_lookup(struct inode
> *dir, struct dentry *dentry,
>  			    dentry->d_name.len) &&
>  		    !is_root_ceph_dentry(dir, dentry) &&
>  		    ceph_test_mount_opt(fsc, DCACHE) &&
> +		    ceph_snap(dir) == CEPH_NOSNAP &&
>  		    __ceph_dir_is_complete(ci) &&
>  		    __ceph_caps_issued_mask_metric(ci,
> CEPH_CAP_FILE_SHARED, 1)) {
>  			__ceph_touch_fmode(ci, mdsc,
> CEPH_FILE_MODE_RD);
> diff --git a/fs/ceph/inode.c b/fs/ceph/inode.c
> index 61d7c0b8161f..d52e2b389e0b 100644
> --- a/fs/ceph/inode.c
> +++ b/fs/ceph/inode.c
> @@ -1814,7 +1814,8 @@ int ceph_fill_trace(struct super_block *sb,
> struct ceph_mds_request *req)
>  				ceph_dir_clear_ordered(dir);
>  				d_delete(dn);
>  			} else if (have_lease) {
> -				if (d_unhashed(dn))
> +				if (d_unhashed(dn) &&
> +				    ceph_snap(dir) == CEPH_NOSNAP)
>  					d_add(dn, NULL);
>  			}
>  
> 
> ---
> base-commit: 602bb4525c8146865b7f6e44c81d54bf97861aed
> change-id: 20260722-b4-snap-negative-dentry-bbf74719a151
> 
> Best regards,
> --  
> Xiubo Li <xiubo.li@clyso.com>
> 
> 

Makes sense.

Reviewed-by: Viacheslav Dubeyko <slava@dubeyko.com>

Thanks,
Slava.

      reply	other threads:[~2026-07-23 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  6:28 Xiubo Li via B4 Relay
2026-07-23 16:52 ` Viacheslav Dubeyko [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=f8be59729e99bfc9182d74eb0fe6f1782dbc1dc8.camel@dubeyko.com \
    --to=slava@dubeyko.com \
    --cc=amarkuze@redhat.com \
    --cc=apataki@flatironinstitute.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dparmar@redhat.com \
    --cc=idryomov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiubo.li@clyso.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

all inboxes | Powered by JetHome®