From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Satya Tangirala <satyat@google.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
Eric Biggers <ebiggers@kernel.org>, Chao Yu <chao@kernel.org>,
linux-kernel@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v2 0/3] add support for metadata encryption to F2FS
Date: Thu, 17 Dec 2020 18:34:27 -0500 [thread overview]
Message-ID: <X9vrA/h8et4japdI@mit.edu> (raw)
In-Reply-To: <X9vEwgHlURxvxqiM@google.com>
On Thu, Dec 17, 2020 at 08:51:14PM +0000, Satya Tangirala wrote:
> On Thu, Dec 17, 2020 at 01:08:49PM -0500, Theodore Y. Ts'o wrote:
> > On Thu, Dec 17, 2020 at 03:04:32PM +0000, Satya Tangirala wrote:
> > > This patch series adds support for metadata encryption to F2FS using
> > > blk-crypto.
> >
> > Is there a companion patch series needed so that f2fstools can
> > check/repair a file system with metadata encryption enabled?
> >
> > - Ted
> Yes! It's at
> https://lore.kernel.org/linux-f2fs-devel/20201217151013.1513045-1-satyat@google.com/
Cool, I've been meaning to update f2fs-tools in Debian, and including
these patches will allow us to generate {kvm,gce,android}-xfstests
images with this support. I'm hoping to get to it sometime betweeen
Christmas and New Year's.
I guess there will need to be some additional work needed to create
the f2fs image with a fixed keys for a particular file system in
xfstests-bld, and then mounting and checking said image with the
appropriatre keys as well. Is that something you've put together?
Cheers,
- Ted
next prev parent reply other threads:[~2020-12-17 23:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 15:04 [PATCH v2 0/3] add support for metadata encryption to F2FS Satya Tangirala
2020-12-17 15:04 ` [PATCH v2 1/3] fscrypt, f2fs: replace fscrypt_get_devices with fscrypt_get_device Satya Tangirala
2020-12-17 15:04 ` [PATCH v2 2/3] fscrypt: Add metadata encryption support Satya Tangirala
2020-12-17 15:24 ` Satya Tangirala
2020-12-24 11:31 ` Satya Tangirala
2021-01-29 20:41 ` Eric Biggers
2020-12-17 15:04 ` [PATCH v2 3/3] f2fs: " Satya Tangirala
2021-01-29 20:57 ` Eric Biggers
2020-12-17 15:16 ` [PATCH v2 0/3] add support for metadata encryption to F2FS Satya Tangirala
2020-12-17 18:08 ` Theodore Y. Ts'o
2020-12-17 20:51 ` Satya Tangirala
2020-12-17 23:34 ` Theodore Y. Ts'o [this message]
2020-12-18 0:05 ` Satya Tangirala
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=X9vrA/h8et4japdI@mit.edu \
--to=tytso@mit.edu \
--cc=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=satyat@google.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;
as well as URLs for NNTP newsgroup(s).