From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL for v6.11] vfs casefold
Date: Fri, 12 Jul 2024 15:57:15 +0200 [thread overview]
Message-ID: <20240712-vfs-casefold-816b45ce2d57@brauner> (raw)
Hey Linus,
/* Summary */
This contains some work to simplify the handling of casefolded names:
- Simplify the handling of casefolded names in f2fs and ext4 by keeping the
names as a qstr to avoiding unnecessary conversions.
- Introduce a new generic_ci_match() libfs case-insensitive lookup helper and
use it in both f2fs and ext4 allowing to remove the filesystem specific
implementations.
- Remove a bunch of ifdefs by making the unicode built checks part of the code
flow.
/* Testing */
clang: Debian clang version 16.0.6 (26)
gcc: (Debian 13.2.0-24)
All patches are based on v6.10-rc1 and have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
No known conflicts.
The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:
Linux 6.10-rc1 (2024-05-26 15:20:12 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.11.casefold
for you to fetch changes up to 28add38d545f445f01eec844b85eed4593c31733:
f2fs: Move CONFIG_UNICODE defguards into the code flow (2024-06-07 17:00:45 +0200)
Please consider pulling these changes from the signed vfs-6.11.casefold tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.11.casefold
----------------------------------------------------------------
Gabriel Krisman Bertazi (7):
ext4: Simplify the handling of cached casefolded names
f2fs: Simplify the handling of cached casefolded names
libfs: Introduce case-insensitive string comparison helper
ext4: Reuse generic_ci_match for ci comparisons
f2fs: Reuse generic_ci_match for ci comparisons
ext4: Move CONFIG_UNICODE defguards into the code flow
f2fs: Move CONFIG_UNICODE defguards into the code flow
fs/ext4/crypto.c | 10 +----
fs/ext4/ext4.h | 35 +++++++++------
fs/ext4/namei.c | 122 ++++++++++++++++-------------------------------------
fs/ext4/super.c | 4 +-
fs/f2fs/dir.c | 105 ++++++++++++++-------------------------------
fs/f2fs/f2fs.h | 16 ++++++-
fs/f2fs/namei.c | 10 ++---
fs/f2fs/recovery.c | 9 +---
fs/f2fs/super.c | 8 ++--
fs/libfs.c | 74 ++++++++++++++++++++++++++++++++
include/linux/fs.h | 4 ++
11 files changed, 195 insertions(+), 202 deletions(-)
next reply other threads:[~2024-07-12 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 13:57 Christian Brauner [this message]
2024-07-15 20:34 ` [GIT PULL for v6.11] vfs casefold pr-tracker-bot
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=20240712-vfs-casefold-816b45ce2d57@brauner \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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