From: "Theodore Ts'o" <tytso@mit.edu>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: viro@zeniv.linux.org.uk, brauner@kernel.org, ebiggers@kernel.org,
jaegeuk@kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v4 0/7] Support negative dentries on case-insensitive ext4 and f2fs
Date: Thu, 27 Jul 2023 14:13:39 -0400 [thread overview]
Message-ID: <20230727181339.GH30264@mit.edu> (raw)
In-Reply-To: <20230727172843.20542-1-krisman@suse.de>
On Thu, Jul 27, 2023 at 01:28:36PM -0400, Gabriel Krisman Bertazi wrote:
> This is the v4 of the negative dentry support on case-insensitive
> directories. It doesn't have any functional changes from v1. It applies
> Eric's comments to bring the flags check closet together, improve the
> documentation and improve comments in the code. I also relooked at the
> locks to ensure the inode read lock is indeed enough in the lookup_slow
> path.
Al, Christian, any thoughts or preferences for how we should handle
this patch series? I'm willing to take it through the ext4 tree, but
since it has vfs, ext4, and f2fs changes (and the bulk of the changes
are in the vfs), perhaps it should go through the vfs tree?
Also, Christian, I notice one of the five VFS patches in the series
has your Reviewed-by tag, but not the others? Is that because you
haven't had a chance to make a final determination on those patches,
or you have outstanding comments still to be addressed?
Cheers,
- Ted
next prev parent reply other threads:[~2023-07-27 18:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 17:28 [PATCH v4 0/7] Support negative dentries on case-insensitive ext4 and f2fs Gabriel Krisman Bertazi
2023-07-27 17:28 ` [PATCH v4 1/7] fs: Expose name under lookup to d_revalidate hook Gabriel Krisman Bertazi
2023-07-28 14:00 ` Christian Brauner
2023-07-28 15:49 ` Gabriel Krisman Bertazi
2023-07-27 17:28 ` [PATCH v4 2/7] fs: Add DCACHE_CASEFOLDED_NAME flag Gabriel Krisman Bertazi
2023-07-29 4:34 ` Eric Biggers
2023-07-27 17:28 ` [PATCH v4 3/7] libfs: Validate negative dentries in case-insensitive directories Gabriel Krisman Bertazi
2023-07-28 13:06 ` Christian Brauner
2023-07-28 15:09 ` Gabriel Krisman Bertazi
2023-07-29 4:18 ` Eric Biggers
2023-07-29 4:20 ` Eric Biggers
2023-08-03 17:37 ` Gabriel Krisman Bertazi
2023-08-04 4:41 ` Eric Biggers
2023-08-08 1:33 ` Gabriel Krisman Bertazi
2023-07-29 4:51 ` Eric Biggers
2023-08-03 16:56 ` Gabriel Krisman Bertazi
2023-07-27 17:28 ` [PATCH v4 4/7] libfs: Chain encryption checks after case-insensitive revalidation Gabriel Krisman Bertazi
2023-07-27 17:28 ` [PATCH v4 5/7] libfs: Merge encrypted_ci_dentry_ops and ci_dentry_ops Gabriel Krisman Bertazi
2023-07-27 17:28 ` [PATCH v4 6/7] ext4: Enable negative dentries on case-insensitive lookup Gabriel Krisman Bertazi
2023-07-27 17:28 ` [PATCH v4 7/7] f2fs: " Gabriel Krisman Bertazi
2023-07-27 18:13 ` Theodore Ts'o [this message]
2023-07-27 18:39 ` [PATCH v4 0/7] Support negative dentries on case-insensitive ext4 and f2fs Gabriel Krisman Bertazi
2023-07-27 19:41 ` Theodore Ts'o
2023-07-28 7:45 ` Christian Brauner
2023-07-28 11:21 ` Christian Brauner
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=20230727181339.GH30264@mit.edu \
--to=tytso@mit.edu \
--cc=brauner@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=krisman@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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).