From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: Lukas Czerner <lczerner@redhat.com>,
Jeff Layton <jlayton@kernel.org>, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [f2fs-dev] [PATCH v3 0/5] test_dummy_encryption fixes and cleanups
Date: Fri, 13 May 2022 16:16:00 -0700 [thread overview]
Message-ID: <20220513231605.175121-1-ebiggers@kernel.org> (raw)
This series cleans up and fixes the way that ext4 and f2fs handle the
test_dummy_encryption mount option.
Some patches from v2 were already applied to the fscrypt and f2fs trees.
This series just includes the remaining patches. Patches 1-2 can be
applied to the ext4 tree now. The remaining patches will need to wait
until their prerequisites get merged via the fscrypt tree.
Changed from v2 (besides the omitted patches as mentioned above):
- Split the parse_apply_sb_mount_options() fix into its own patch
- Fixed a couple bugs in
"ext4: fix up test_dummy_encryption handling for new mount API"
Eric Biggers (5):
ext4: fix memory leak in parse_apply_sb_mount_options()
ext4: only allow test_dummy_encryption when supported
ext4: fix up test_dummy_encryption handling for new mount API
f2fs: use the updated test_dummy_encryption helper functions
fscrypt: remove fscrypt_set_test_dummy_encryption()
fs/crypto/policy.c | 13 ---
fs/ext4/ext4.h | 6 --
fs/ext4/super.c | 180 +++++++++++++++++++++++-----------------
fs/f2fs/super.c | 29 +++++--
include/linux/fscrypt.h | 2 -
5 files changed, 124 insertions(+), 106 deletions(-)
--
2.36.1
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: Jeff Layton <jlayton@kernel.org>,
Lukas Czerner <lczerner@redhat.com>,
Theodore Ts'o <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH v3 0/5] test_dummy_encryption fixes and cleanups
Date: Fri, 13 May 2022 16:16:00 -0700 [thread overview]
Message-ID: <20220513231605.175121-1-ebiggers@kernel.org> (raw)
This series cleans up and fixes the way that ext4 and f2fs handle the
test_dummy_encryption mount option.
Some patches from v2 were already applied to the fscrypt and f2fs trees.
This series just includes the remaining patches. Patches 1-2 can be
applied to the ext4 tree now. The remaining patches will need to wait
until their prerequisites get merged via the fscrypt tree.
Changed from v2 (besides the omitted patches as mentioned above):
- Split the parse_apply_sb_mount_options() fix into its own patch
- Fixed a couple bugs in
"ext4: fix up test_dummy_encryption handling for new mount API"
Eric Biggers (5):
ext4: fix memory leak in parse_apply_sb_mount_options()
ext4: only allow test_dummy_encryption when supported
ext4: fix up test_dummy_encryption handling for new mount API
f2fs: use the updated test_dummy_encryption helper functions
fscrypt: remove fscrypt_set_test_dummy_encryption()
fs/crypto/policy.c | 13 ---
fs/ext4/ext4.h | 6 --
fs/ext4/super.c | 180 +++++++++++++++++++++++-----------------
fs/f2fs/super.c | 29 +++++--
include/linux/fscrypt.h | 2 -
5 files changed, 124 insertions(+), 106 deletions(-)
--
2.36.1
next reply other threads:[~2022-05-13 23:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 23:16 Eric Biggers [this message]
2022-05-13 23:16 ` [PATCH v3 0/5] test_dummy_encryption fixes and cleanups Eric Biggers
2022-05-13 23:16 ` [f2fs-dev] [PATCH v3 1/5] ext4: fix memory leak in parse_apply_sb_mount_options() Eric Biggers
2022-05-13 23:16 ` Eric Biggers
2022-05-14 12:09 ` [f2fs-dev] " Ritesh Harjani
2022-05-14 12:09 ` Ritesh Harjani
2022-05-19 2:10 ` Theodore Ts'o
2022-05-19 2:10 ` [f2fs-dev] " Theodore Ts'o
2022-05-13 23:16 ` [f2fs-dev] [PATCH v3 2/5] ext4: only allow test_dummy_encryption when supported Eric Biggers
2022-05-13 23:16 ` Eric Biggers
2022-05-19 2:11 ` Theodore Ts'o
2022-05-19 2:11 ` [f2fs-dev] " Theodore Ts'o
2022-05-13 23:16 ` [f2fs-dev] [PATCH v3 3/5] ext4: fix up test_dummy_encryption handling for new mount API Eric Biggers
2022-05-13 23:16 ` Eric Biggers
2022-05-13 23:16 ` [f2fs-dev] [PATCH v3 4/5] f2fs: use the updated test_dummy_encryption helper functions Eric Biggers
2022-05-13 23:16 ` Eric Biggers
2022-05-19 11:21 ` [f2fs-dev] " Chao Yu
2022-05-19 11:21 ` Chao Yu
2022-05-13 23:16 ` [f2fs-dev] [PATCH v3 5/5] fscrypt: remove fscrypt_set_test_dummy_encryption() Eric Biggers
2022-05-13 23:16 ` Eric Biggers
2022-08-15 18:48 ` [f2fs-dev] " Eric Biggers
2022-08-15 18:48 ` Eric Biggers
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=20220513231605.175121-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jlayton@kernel.org \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.