lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 1 Oct 2021 21:21:33 -0400
From:   "Theodore Ts'o" <>
To:     Gabriel Krisman Bertazi <>
Cc:     Shreeya Patel <>,,,,,,
Subject: Re: [PATCH 2/2] fs: ext4: Fix the inconsistent name exposed by

On Fri, Oct 01, 2021 at 03:11:30PM -0400, Gabriel Krisman Bertazi wrote:
> The dcache name is exposed in more places, like /proc/mounts.  We have a
> bug reported against flatpak where its initialization code bind mounts a
> directory that was previously touched with a different case combination,
> and then checks /proc/mounts in a case-sensitive way to see if the mount
> succeeded.  This code now regresses on CI directories because the name
> it asked to bind mount is not found in /proc/mounts.

Ah, thanks for the context.  That makes sense.

> I think the more reasonable approach is to save the disk exact name on
> the dcache, because that is the only version that doesn't change based
> on who won the race for the first lookup.

What about the alternative of storing the casefolded name?  The
advantage of using the casefolded name is that we can always casefold
the name, where as in the case of a negative dentry, there is no disk
exact name to use (since by definition there is no on-disk name).

      	      	  	    	       - Ted

Powered by blists - more mailing lists