From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Shreeya Patel <shreeya.patel@collabora.com>
Cc: tytso@mit.edu, viro@zeniv.linux.org.uk, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH 1/2] fs: dcache: Handle case-exact lookup in d_alloc_parallel
Date: Fri, 01 Oct 2021 14:35:32 -0400 [thread overview]
Message-ID: <87a6js61aj.fsf@collabora.com> (raw)
In-Reply-To: <0b8fd2677b797663bfcb97f6aa108193fedf9767.1632909358.git.shreeya.patel@collabora.com> (Shreeya Patel's message of "Wed, 29 Sep 2021 16:23:38 +0530")
Shreeya Patel <shreeya.patel@collabora.com> writes:
> There is a soft hang caused by a deadlock in d_alloc_parallel which
> waits up on lookups to finish for the dentries in the parent directory's
> hash_table.
> In case when d_add_ci is called from the fs layer's lookup functions,
> the dentry being looked up is already in the hash table (created before
> the fs lookup function gets called). We should not be processing the
> same dentry that is being looked up, hence, in case of case-insensitive
> filesystems we are making it a case-exact match to prevent this from
> happening.
>
> Signed-off-by: Shreeya Patel <shreeya.patel@collabora.com>
> ---
> fs/dcache.c | 20 ++++++++++++++++++--
> 1 file changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/fs/dcache.c b/fs/dcache.c
> index cf871a81f4fd..2a28ab64a165 100644
> --- a/fs/dcache.c
> +++ b/fs/dcache.c
> @@ -2565,6 +2565,15 @@ static void d_wait_lookup(struct dentry *dentry)
> }
> }
>
> +static inline bool d_same_exact_name(const struct dentry *dentry,
> + const struct dentry *parent,
> + const struct qstr *name)
> +{
> + if (dentry->d_name.len != name->len)
> + return false;
> + return dentry_cmp(dentry, name->name, name->len) == 0;
> +}
I don't like the idea of having a flavor of a dentry comparison function
that doesn't invoke d_compare. In particular because d_compare might be
used for all sorts of things, and this fix is really specific to the
case-insensitive case.
Would it be possible to fold this change into generic_ci_d_compare? If
we could flag the dentry as part of a parallel lookup under the relevant
condition, generic_ci_d_compare could simply return immediately in
such case.
> +
> struct dentry *d_alloc_parallel(struct dentry *parent,
> const struct qstr *name,
> wait_queue_head_t *wq)
> @@ -2575,6 +2584,7 @@ struct dentry *d_alloc_parallel(struct dentry *parent,
> struct dentry *new = d_alloc(parent, name);
> struct dentry *dentry;
> unsigned seq, r_seq, d_seq;
> + int ci_dir = IS_CASEFOLDED(parent->d_inode);
>
> if (unlikely(!new))
> return ERR_PTR(-ENOMEM);
> @@ -2626,8 +2636,14 @@ struct dentry *d_alloc_parallel(struct dentry *parent,
> continue;
> if (dentry->d_parent != parent)
> continue;
> - if (!d_same_name(dentry, parent, name))
> - continue;
> + if (ci_dir) {
> + if (!d_same_exact_name(dentry, parent, name))
> + continue;
> + } else {
As is, this is problematic because d_alloc_parallel is also part of the
lookup path (see lookup_open, lookup_slow). In those cases, you want to
do the CI comparison, to prevent racing two tasks creating a dentry
differing only by case.
> + if (!d_same_name(dentry, parent, name))
> + continue;
> + }
> +
> hlist_bl_unlock(b);
> /* now we can try to grab a reference */
> if (!lockref_get_not_dead(&dentry->d_lockref)) {
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2021-10-01 18:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 10:53 [PATCH 0/2] Handle a soft hang and the inconsistent name issue Shreeya Patel
2021-09-29 10:53 ` [PATCH 1/2] fs: dcache: Handle case-exact lookup in d_alloc_parallel Shreeya Patel
2021-10-01 18:35 ` Gabriel Krisman Bertazi [this message]
2021-10-03 13:52 ` Al Viro
2021-10-03 13:38 ` Al Viro
2021-10-05 13:09 ` Shreeya Patel
2021-09-29 10:53 ` [PATCH 2/2] fs: ext4: Fix the inconsistent name exposed by /proc/self/cwd Shreeya Patel
2021-10-01 18:41 ` Theodore Ts'o
2021-10-01 19:11 ` Gabriel Krisman Bertazi
2021-10-02 1:21 ` Theodore Ts'o
2021-10-14 21:54 ` Gabriel Krisman Bertazi
2021-10-01 18:16 ` [PATCH 0/2] Handle a soft hang and the inconsistent name issue Gabriel Krisman Bertazi
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=87a6js61aj.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=adilger.kernel@dilger.ca \
--cc=kernel@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shreeya.patel@collabora.com \
--cc=tytso@mit.edu \
--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).