lists.openwall.net | 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 linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20240131010023.GE2020@sol.localdomain> Date: Tue, 30 Jan 2024 17:00:23 -0800 From: Eric Biggers <ebiggers@...nel.org> To: Gabriel Krisman Bertazi <krisman@...e.de> Cc: viro@...iv.linux.org.uk, jaegeuk@...nel.org, tytso@....edu, amir73il@...il.com, linux-ext4@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net, linux-fsdevel@...r.kernel.org Subject: Re: [PATCH v5 07/12] libfs: Merge encrypted_ci_dentry_ops and ci_dentry_ops On Mon, Jan 29, 2024 at 05:43:25PM -0300, Gabriel Krisman Bertazi wrote: > In preparation to get case-insensitive dentry operations from > sb->s_d_op again, use the same structure for case-insensitive > filesystems with and without fscrypt. > > This means that on a casefolded filesystem without fscrypt, we end up Again, we shouldn't use the term "case-insensitive filesystem" (or casefolded filesystem) when we actually mean "case-insensitive capable filesystem", or more precisely "filesystem that supports case-insensitive directories". Real case-insensitive filesystems like FAT are not relevant here. > Also, since the first fscrypt_d_revalidate will call d_set_always_valid for us This is outdated. - Eric
Powered by blists - more mailing lists