From: Satya Tangirala <satyat@google.com> To: "Theodore Y. Ts'o" <tytso@mit.edu> 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: Fri, 18 Dec 2020 00:05:07 +0000 [thread overview] Message-ID: <X9vyM0jb91Q7aBJW@google.com> (raw) In-Reply-To: <X9vrA/h8et4japdI@mit.edu> On Thu, Dec 17, 2020 at 06:34:27PM -0500, Theodore Y. Ts'o wrote: > 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? > I did put something together that sets up metadata encryption on the disks used by kvm-xfstests. The main code changes were to add a fixed metadata encryption key with keyctl, and export MKFS_OPTIONS with the metadata encryption options. The mkfs options are the only options that need direct modification because the rest of the tools (fsck/dump etc.) automatically do the right thing if the FS superblock has the metadata encryption options. But the rest of the tools do need the metadata encryption key to be present, and some xfstests/other parts of the harness code clear the keyrings directly, so I had a few more hacky changes to re-add the keys when they're cleared. Some more hacky changes were needed because some xfstests override MKFS_OPTIONS. I'll be happy to send what I have to you/put it up somewhere. I'll also try to clean up the code a little, but my knowledge of xfstests is definitely limited so it might take a little while. > Cheers, > > - Ted
WARNING: multiple messages have this Message-ID (diff)
From: Satya Tangirala via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net> To: "Theodore Y. Ts'o" <tytso@mit.edu> Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, Eric Biggers <ebiggers@kernel.org>, linux-fscrypt@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org> Subject: Re: [f2fs-dev] [PATCH v2 0/3] add support for metadata encryption to F2FS Date: Fri, 18 Dec 2020 00:05:07 +0000 [thread overview] Message-ID: <X9vyM0jb91Q7aBJW@google.com> (raw) In-Reply-To: <X9vrA/h8et4japdI@mit.edu> On Thu, Dec 17, 2020 at 06:34:27PM -0500, Theodore Y. Ts'o wrote: > 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? > I did put something together that sets up metadata encryption on the disks used by kvm-xfstests. The main code changes were to add a fixed metadata encryption key with keyctl, and export MKFS_OPTIONS with the metadata encryption options. The mkfs options are the only options that need direct modification because the rest of the tools (fsck/dump etc.) automatically do the right thing if the FS superblock has the metadata encryption options. But the rest of the tools do need the metadata encryption key to be present, and some xfstests/other parts of the harness code clear the keyrings directly, so I had a few more hacky changes to re-add the keys when they're cleared. Some more hacky changes were needed because some xfstests override MKFS_OPTIONS. I'll be happy to send what I have to you/put it up somewhere. I'll also try to clean up the code a little, but my knowledge of xfstests is definitely limited so it might take a little while. > Cheers, > > - Ted _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2020-12-18 0:05 UTC|newest] Thread overview: 26+ 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 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel 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 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel 2020-12-17 15:04 ` [PATCH v2 2/3] fscrypt: Add metadata encryption support Satya Tangirala 2020-12-17 15:04 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel 2020-12-17 15:24 ` Satya Tangirala 2020-12-17 15:24 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel 2020-12-24 11:31 ` Satya Tangirala 2020-12-24 11:31 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel 2021-01-29 20:41 ` Eric Biggers 2021-01-29 20:41 ` [f2fs-dev] " Eric Biggers 2020-12-17 15:04 ` [PATCH v2 3/3] f2fs: " Satya Tangirala 2020-12-17 15:04 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel 2021-01-29 20:57 ` Eric Biggers 2021-01-29 20:57 ` [f2fs-dev] " Eric Biggers 2020-12-17 15:16 ` [PATCH v2 0/3] add support for metadata encryption to F2FS Satya Tangirala 2020-12-17 15:16 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel 2020-12-17 18:08 ` Theodore Y. Ts'o 2020-12-17 18:08 ` [f2fs-dev] " Theodore Y. Ts'o 2020-12-17 20:51 ` Satya Tangirala 2020-12-17 20:51 ` [f2fs-dev] " Satya Tangirala via Linux-f2fs-devel 2020-12-17 23:34 ` Theodore Y. Ts'o 2020-12-17 23:34 ` [f2fs-dev] " Theodore Y. Ts'o 2020-12-18 0:05 ` Satya Tangirala [this message] 2020-12-18 0:05 ` Satya Tangirala via Linux-f2fs-devel
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=X9vyM0jb91Q7aBJW@google.com \ --to=satyat@google.com \ --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=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: linkBe 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.