mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "André Almeida" <andrealmeid@igalia.com>
To: Amir Goldstein <amir73il@gmail.com>, NeilBrown <neil@brown.name>
Cc: Miklos Szeredi <miklos@szeredi.hu>, Theodore Tso <tytso@mit.edu>,
	Gabriel Krisman Bertazi <krisman@kernel.org>,
	linux-unionfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	kernel-dev@igalia.com
Subject: Re: [PATCH v6 9/9] ovl: Support mounting case-insensitive enabled layers
Date: Wed, 27 Aug 2025 17:37:26 -0300	[thread overview]
Message-ID: <5934fe16-32e7-425a-b4ee-cdcb77dd751a@igalia.com> (raw)
In-Reply-To: <CAOQ4uxj551a7cvjpcYEyTLtsEXw9OxHtTc-VSm170J5pWtwoUQ@mail.gmail.com>

Em 27/08/2025 15:06, Amir Goldstein escreveu:

[...]

> 
> The reason is this:
> 
> static struct dentry *ext4_lookup(...
> {
> ...
>          if (IS_ENABLED(CONFIG_UNICODE) && !inode && IS_CASEFOLDED(dir)) {
>                  /* Eventually we want to call d_add_ci(dentry, NULL)
>                   * for negative dentries in the encoding case as
>                   * well.  For now, prevent the negative dentry
>                   * from being cached.
>                   */
>                  return NULL;
>          }
> 
>          return d_splice_alias(inode, dentry);
> }
> 
> Neil,
> 
> Apparently, the assumption that
> ovl_lookup_temp() => ovl_lookup_upper() => lookup_one()
> returns a hashed dentry is not always true.
> 
> It may be always true for all the filesystems that are currently
> supported as an overlayfs
> upper layer fs (?), but it does not look like you can count on this
> for the wider vfs effort
> and we should try to come up with a solution for ovl_parent_lock()
> that will allow enabling
> casefolding on overlayfs layers.
> 
> This patch seems to work. WDYT?
> 
> Thanks,
> Amir.
> 

Thank you for the fix!

> commit 5dfcd10378038637648f3f422e3d5097eb6faa5f
> Author: Amir Goldstein <amir73il@gmail.com>
> Date:   Wed Aug 27 19:55:26 2025 +0200
> 
>      ovl: adapt ovl_parent_lock() to casefolded directories
> 
>      e8bd877fb76bb9f3 ("ovl: fix possible double unlink") added a sanity

Just to make checkpatch happy, this should be

Commit e8bd877fb76b ("ovl: fix possible double unlink") added a sanity

>      check of !d_unhashed(child) to try to verify that child dentry was not
>      unlinked while parent dir was unlocked.
> 
>      This "was not unlink" check has a false positive result in the case of
>      casefolded parent dir, because in that case, ovl_create_temp() returns
>      an unhashed dentry.
> 
>      Change the "was not unlinked" check to use cant_mount(child).
>      cant_mount(child) means that child was unlinked while we have been
>      holding a reference to child, so it could not have become negative.
> 
>      This fixes the error in ovl_parent_lock() in ovl_check_rename_whiteout()
>      after ovl_create_temp() and allows mount of overlayfs with casefolding
>      enabled layers.
> 
>      Reported-by: André Almeida <andrealmeid@igalia.com>
>      Link: https://lore.kernel.org/r/18704e8c-c734-43f3-bc7c-b8be345e1bf5@igalia.com/

I think the correct chain here is:

Reported-by: André Almeida <andrealmeid@igalia.com>
Closes: 
https://lore.kernel.org/r/18704e8c-c734-43f3-bc7c-b8be345e1bf5@igalia.com/
Fixes: e8bd877fb76b ("ovl: fix possible double unlink")

>      Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> 

Reviewed-by: André Almeida <andrealmeid@igalia.com>

> diff --git a/fs/overlayfs/util.c b/fs/overlayfs/util.c
> index bec4a39d1b97c..bffbb59776720 100644
> --- a/fs/overlayfs/util.c
> +++ b/fs/overlayfs/util.c
> @@ -1551,9 +1551,23 @@ void ovl_copyattr(struct inode *inode)
> 
>   int ovl_parent_lock(struct dentry *parent, struct dentry *child)
>   {
> +       bool is_unlinked;
> +
>          inode_lock_nested(parent->d_inode, I_MUTEX_PARENT);
> -       if (!child ||
> -           (!d_unhashed(child) && child->d_parent == parent))
> +       if (!child)
> +               return 0;
> +
> +       /*
> +        * After re-acquiring parent dir lock, verify that child was not moved
> +        * to another parent and that it was not unlinked. cant_mount() means
> +        * that child was unlinked while parent was unlocked. Since we are
> +        * holding a reference to child, it could not have become negative.
> +        * d_unhashed(child) is not a strong enough indication for unlinked,
> +        * because with casefolded parent dir, ovl_create_temp() returns an
> +        * unhashed dentry.
> +        */
> +       is_unlinked = cant_mount(child) || WARN_ON_ONCE(d_is_negative(child));
> +       if (!is_unlinked && child->d_parent == parent)
>                  return 0;
> 
>          inode_unlock(parent->d_inode);


  reply	other threads:[~2025-08-27 20:37 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22 14:17 [PATCH v6 0/9] ovl: Enable support for casefold layers André Almeida
2025-08-22 14:17 ` [PATCH v6 1/9] fs: Create sb_encoding() helper André Almeida
2025-08-25  9:19   ` Gabriel Krisman Bertazi
2025-08-25 12:38   ` Gabriel Krisman Bertazi
2025-08-25 15:28     ` Amir Goldstein
2025-08-22 14:17 ` [PATCH v6 2/9] fs: Create sb_same_encoding() helper André Almeida
2025-08-23 10:02   ` Amir Goldstein
2025-08-25  9:24   ` Gabriel Krisman Bertazi
2025-08-22 14:17 ` [PATCH v6 3/9] ovl: Prepare for mounting case-insensitive enabled layers André Almeida
2025-08-25 10:42   ` Gabriel Krisman Bertazi
2025-08-22 14:17 ` [PATCH v6 4/9] ovl: Create ovl_casefold() to support casefolded strncmp() André Almeida
2025-08-22 16:53   ` Amir Goldstein
2025-08-25 11:09   ` Gabriel Krisman Bertazi
2025-08-25 15:27     ` Amir Goldstein
2025-08-25 15:45       ` Amir Goldstein
2025-08-25 17:11         ` Gabriel Krisman Bertazi
2025-08-26  1:34           ` Gabriel Krisman Bertazi
2025-08-26  7:19             ` Amir Goldstein
2025-08-26 15:02               ` Gabriel Krisman Bertazi
2025-08-26 19:58                 ` André Almeida
2025-08-27  9:28                   ` Amir Goldstein
2025-08-26 20:01               ` André Almeida
2025-08-27 20:45               ` André Almeida
2025-08-28 11:09                 ` Amir Goldstein
2025-08-22 14:17 ` [PATCH v6 5/9] ovl: Ensure that all layers have the same encoding André Almeida
2025-08-25 11:17   ` Gabriel Krisman Bertazi
2025-08-25 15:32     ` Amir Goldstein
2025-08-26 20:12       ` André Almeida
2025-08-27  9:17         ` Amir Goldstein
2025-08-22 14:17 ` [PATCH v6 6/9] ovl: Set case-insensitive dentry operations for ovl sb André Almeida
2025-08-25 11:24   ` Gabriel Krisman Bertazi
2025-08-25 15:34     ` Amir Goldstein
2025-08-26 20:13       ` André Almeida
2025-08-22 14:17 ` [PATCH v6 7/9] ovl: Add S_CASEFOLD as part of the inode flag to be copied André Almeida
2025-08-22 14:17 ` [PATCH v6 8/9] ovl: Check for casefold consistency when creating new dentries André Almeida
2025-08-22 14:17 ` [PATCH v6 9/9] ovl: Support mounting case-insensitive enabled layers André Almeida
2025-08-22 16:34   ` Amir Goldstein
2025-08-22 16:47     ` André Almeida
2025-08-22 19:17       ` Amir Goldstein
2025-08-25 13:31         ` André Almeida
2025-08-26  7:31           ` Amir Goldstein
2025-08-26 19:01             ` André Almeida
2025-08-27 18:06               ` Amir Goldstein
2025-08-27 20:37                 ` André Almeida [this message]
2025-08-27 23:58                 ` NeilBrown
2025-08-28  3:15                   ` Gabriel Krisman Bertazi
2025-08-28  7:25                     ` Amir Goldstein
2025-08-28 16:44                       ` Amir Goldstein
2025-08-29  1:27                         ` NeilBrown
2025-08-29  1:25                       ` NeilBrown
2025-08-29  9:31                         ` Amir Goldstein
2025-09-01 22:02                           ` NeilBrown
2025-08-22 19:28 ` [syzbot ci] Re: ovl: Enable support for casefold layers syzbot ci

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=5934fe16-32e7-425a-b4ee-cdcb77dd751a@igalia.com \
    --to=andrealmeid@igalia.com \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=kernel-dev@igalia.com \
    --cc=krisman@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=neil@brown.name \
    --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

all inboxes | Powered by JetHome®