From: Ian Kent <raven@themaw.net>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Chengguang Xu <cgxu519@mykernel.net>,
Miklos Szeredi <miklos@szeredi.hu>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: [RFC PATCH v3 0/9] Suppress negative dentry
Date: Mon, 18 May 2020 18:39:31 +0800 [thread overview]
Message-ID: <cd4f03a3820195cddeb489e66892c3d5e13b8b48.camel@themaw.net> (raw)
In-Reply-To: <cfc4e94f6667eabee664b63cc23051e9d816456c.camel@themaw.net>
On Mon, 2020-05-18 at 18:26 +0800, Ian Kent wrote:
>
> Now d_splice_alias() is pretty complicated but, if passed a NULL
> dentry it amounts to calling __d_add(dentry, NULL) which produces
> a negative hashed dentry, a decision made by ext4 ->lookup() (and
> I must say typical of the very few ways such dentries get into
> the dcache).
Oh, rather that's a NULL inode not dentry.
Ian
prev parent reply other threads:[~2020-05-18 10:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 7:20 [RFC PATCH v3 0/9] Suppress negative dentry Chengguang Xu
2020-05-15 7:20 ` [RFC PATCH v3 1/9] fs/dcache: Introduce a new lookup flag LOOKUP_DONTCACHE_NEGATIVE Chengguang Xu
2020-05-15 7:20 ` [RFC PATCH v3 2/9] ovl: Suppress negative dentry in lookup Chengguang Xu
2020-05-15 7:20 ` [RFC PATCH v3 3/9] cifs: Adjust argument for lookup_positive_unlocked() Chengguang Xu
2020-05-15 7:20 ` [RFC PATCH v3 4/9] debugfs: " Chengguang Xu
2020-05-15 7:20 ` [RFC PATCH v3 5/9] ecryptfs: Adjust argument for lookup_one_len_unlocked() Chengguang Xu
2020-05-15 7:20 ` [RFC PATCH v3 6/9] exportfs: " Chengguang Xu
2020-05-15 7:20 ` [RFC PATCH v3 7/9] kernfs: Adjust argument for lookup_positive_unlocked() Chengguang Xu
2020-05-15 7:20 ` [RFC PATCH v3 8/9] nfsd: " Chengguang Xu
2020-05-15 7:20 ` [RFC PATCH v3 9/9] quota: " Chengguang Xu
2020-05-15 7:30 ` [RFC PATCH v3 0/9] Suppress negative dentry Amir Goldstein
2020-05-15 8:25 ` Chengguang Xu
2020-05-15 8:42 ` Miklos Szeredi
2020-05-18 0:53 ` Ian Kent
2020-05-18 5:27 ` Amir Goldstein
2020-05-18 7:52 ` Miklos Szeredi
2020-05-18 8:51 ` Amir Goldstein
2020-05-18 9:17 ` Miklos Szeredi
2020-05-19 5:01 ` cgxu
2020-05-19 8:21 ` Miklos Szeredi
2020-05-19 9:23 ` cgxu
2020-05-20 14:44 ` Miklos Szeredi
2020-05-25 13:37 ` Chengguang Xu
2020-05-25 13:50 ` Miklos Szeredi
2020-05-18 10:26 ` Ian Kent
2020-05-18 10:39 ` Ian Kent [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=cd4f03a3820195cddeb489e66892c3d5e13b8b48.camel@themaw.net \
--to=raven@themaw.net \
--cc=amir73il@gmail.com \
--cc=cgxu519@mykernel.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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).