From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
Daniel Rosenberg <drosen@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Gabriel Krisman Bertazi <krisman@collabora.com>
Subject: Re: [PATCH v12 0/4] Prepare for upcoming Casefolding/Encryption patches
Date: Mon, 24 Aug 2020 16:32:10 -0700 [thread overview]
Message-ID: <20200824233210.GA122905@google.com> (raw)
In-Reply-To: <20200824230015.GA810@sol.localdomain>
On 08/24, Eric Biggers wrote:
> On Mon, Jul 27, 2020 at 09:45:08AM -0700, Eric Biggers wrote:
> > On Mon, Jul 20, 2020 at 10:09:51AM -0700, Eric Biggers wrote:
> > > On Wed, Jul 08, 2020 at 02:12:33AM -0700, Daniel Rosenberg wrote:
> > > > This lays the ground work for enabling casefolding and encryption at the
> > > > same time for ext4 and f2fs. A future set of patches will enable that
> > > > functionality.
> > > >
> > > > These unify the highly similar dentry_operations that ext4 and f2fs both
> > > > use for casefolding. In addition, they improve d_hash by not requiring a
> > > > new string allocation.
> > > >
> > > > Daniel Rosenberg (4):
> > > > unicode: Add utf8_casefold_hash
> > > > fs: Add standard casefolding support
> > > > f2fs: Use generic casefolding support
> > > > ext4: Use generic casefolding support
> > > >
> > >
> > > Ted, are you interested in taking this through the ext4 tree for 5.9?
> > >
> > > - Eric
> >
> > Ping?
> >
>
> Unfortunately this patchset got ignored for 5.9.
>
> Ted, will you have any interest in taking this patchset for 5.10? Or should
> Jaegeuk just take patches 1-3 via the f2fs tree?
fyi; I think I can merge 1-3, if Al has no concern on 1 & 2.
>
> The fscrypt tree is also an option, but I feel it's not really appropriate since
> this patchset is just a refactoring of the existing casefolding support.
>
> More reviews on patches 1-2 would be appreciated too. So far just Gabriel and I
> have reviewed them. I was hoping that other people would review them too.
>
> - Eric
prev parent reply other threads:[~2020-08-24 23:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 9:12 [PATCH v12 0/4] Prepare for upcoming Casefolding/Encryption patches Daniel Rosenberg
2020-07-08 9:12 ` [PATCH v12 1/4] unicode: Add utf8_casefold_hash Daniel Rosenberg
2020-07-08 9:12 ` [PATCH v12 2/4] fs: Add standard casefolding support Daniel Rosenberg
2020-07-08 15:49 ` Eric Biggers
2020-07-08 9:12 ` [PATCH v12 3/4] f2fs: Use generic " Daniel Rosenberg
2020-07-08 17:08 ` Jaegeuk Kim
2020-07-08 9:12 ` [PATCH v12 4/4] ext4: " Daniel Rosenberg
2020-09-21 1:10 ` Gabriel Krisman Bertazi
2020-09-21 18:29 ` Eric Biggers
2020-09-22 6:18 ` Daniel Rosenberg
2020-07-20 17:09 ` [PATCH v12 0/4] Prepare for upcoming Casefolding/Encryption patches Eric Biggers
2020-07-27 16:45 ` Eric Biggers
2020-08-24 23:00 ` Eric Biggers
2020-08-24 23:32 ` Jaegeuk Kim [this message]
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=20200824233210.GA122905@google.com \
--to=jaegeuk@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=drosen@google.com \
--cc=ebiggers@kernel.org \
--cc=kernel-team@android.com \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).