From: Eric Biggers <ebiggers@kernel.org>
To: linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>
Cc: linux-fsdevel@vger.kernel.org,
Gabriel Krisman Bertazi <krisman@suse.de>,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 0/3] Simplify rejection of unexpected casefold inode flag
Date: Mon, 14 Aug 2023 11:29:00 -0700 [thread overview]
Message-ID: <20230814182903.37267-1-ebiggers@kernel.org> (raw)
This series makes unexpected casefold flags on inodes be consistently
rejected early on so that additional validation isn't needed later on
during random filesystem operations. For additional context, refer to
the discussion on patch 1 of
https://lore.kernel.org/linux-fsdevel/20230812004146.30980-1-krisman@suse.de/T/#u
Applies to v6.5-rc6
Eric Biggers (3):
ext4: reject casefold inode flag without casefold feature
ext4: remove redundant checks of s_encoding
libfs: remove redundant checks of s_encoding
fs/ext4/hash.c | 2 +-
fs/ext4/inode.c | 5 ++++-
fs/ext4/namei.c | 6 +++---
fs/libfs.c | 14 ++------------
4 files changed, 10 insertions(+), 17 deletions(-)
base-commit: 2ccdd1b13c591d306f0401d98dedc4bdcd02b421
--
2.41.0
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2023-08-14 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 18:29 Eric Biggers [this message]
2023-08-14 18:29 ` [f2fs-dev] [PATCH 1/3] ext4: reject casefold inode flag without casefold feature Eric Biggers
2023-08-14 19:09 ` Gabriel Krisman Bertazi
2023-08-14 19:24 ` Eric Biggers
2023-08-14 19:52 ` Gabriel Krisman Bertazi
2023-08-14 18:29 ` [f2fs-dev] [PATCH 2/3] ext4: remove redundant checks of s_encoding Eric Biggers
2023-08-14 18:29 ` [f2fs-dev] [PATCH 3/3] libfs: " Eric Biggers
2023-08-24 4:53 ` [f2fs-dev] [PATCH 0/3] Simplify rejection of unexpected casefold inode flag Theodore Ts'o
2023-09-04 18:11 ` patchwork-bot+f2fs
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=20230814182903.37267-1-ebiggers@kernel.org \
--to=ebiggers@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=tytso@mit.edu \
/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).