From: Niels de Vos <ndevos@redhat.com>
To: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Xiubo Li <xiubli@redhat.com>,
Marcel Lauhoff <marcel.lauhoff@suse.com>,
Niels de Vos <ndevos@redhat.com>
Subject: [RFC 0/4] fs: provide per-filesystem options to disable fscrypt
Date: Thu, 10 Nov 2022 15:12:21 +0100 [thread overview]
Message-ID: <20221110141225.2308856-1-ndevos@redhat.com> (raw)
While more filesystems are getting support for fscrypt, it is useful to
be able to disable fscrypt for a selection of filesystems, while
enabling it for others.
The new USE_FS_ENCRYPTION define gets picked up in
include/linux/fscrypt.h. This allows filesystems to choose to use the
empty function definitions, or the functional ones when fscrypt is to be
used with the filesystem.
Using USE_FS_ENCRYPTION is a relatively clean approach, and requires
minimal changes to the filesystems supporting fscrypt. This RFC is
mostly for checking the acceptance of this solution, or if an other
direction is preferred.
---
Niels de Vos (4):
fscrypt: introduce USE_FS_ENCRYPTION
fs: make fscrypt support an ext4 config option
fs: make fscrypt support a f2fs config option
fs: make fscrypt support a UBIFS config option
Documentation/filesystems/fscrypt.rst | 2 +-
fs/crypto/Kconfig | 3 +++
fs/crypto/fscrypt_private.h | 2 ++
fs/ext4/Kconfig | 13 ++++++++++++-
fs/ext4/Makefile | 2 +-
fs/ext4/ext4.h | 12 ++++++++----
fs/ext4/inode.c | 6 +++---
fs/ext4/namei.c | 6 +++---
fs/ext4/super.c | 6 +++---
fs/ext4/sysfs.c | 8 ++++----
fs/f2fs/Kconfig | 15 +++++++++++++--
fs/f2fs/data.c | 2 +-
fs/f2fs/dir.c | 6 +++---
fs/f2fs/f2fs.h | 8 ++++++--
fs/f2fs/super.c | 6 +++---
fs/f2fs/sysfs.c | 8 ++++----
fs/ubifs/Kconfig | 14 ++++++++++++--
fs/ubifs/Makefile | 2 +-
fs/ubifs/sb.c | 4 ++--
fs/ubifs/ubifs.h | 7 +++++--
include/linux/fscrypt.h | 6 +++---
21 files changed, 93 insertions(+), 45 deletions(-)
--
2.37.3
next reply other threads:[~2022-11-10 14:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 14:12 Niels de Vos [this message]
2022-11-10 14:12 ` [RFC 1/4] fscrypt: introduce USE_FS_ENCRYPTION Niels de Vos
2022-11-10 14:12 ` [RFC 2/4] fs: make fscrypt support an ext4 config option Niels de Vos
2022-11-10 14:12 ` [RFC 3/4] fs: make fscrypt support a f2fs " Niels de Vos
2022-11-10 14:12 ` [RFC 4/4] fs: make fscrypt support a UBIFS " Niels de Vos
2022-11-10 15:38 ` [RFC 0/4] fs: provide per-filesystem options to disable fscrypt Theodore Ts'o
2022-11-10 16:47 ` Niels de Vos
2022-11-10 18:15 ` Theodore Ts'o
2022-11-10 18:43 ` Theodore Ts'o
2022-11-18 13:05 ` Niels de Vos
2022-11-14 6:02 ` Christoph Hellwig
2022-11-18 13:13 ` Niels de Vos
2022-11-16 2:10 ` Eric Biggers
2022-11-18 13:25 ` Niels de Vos
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=20221110141225.2308856-1-ndevos@redhat.com \
--to=ndevos@redhat.com \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.lauhoff@suse.com \
--cc=xiubli@redhat.com \
/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