From: Eric Biggers <ebiggers@google.com> To: linux-f2fs-devel@lists.sourceforge.net, Jaegeuk Kim <jaegeuk@kernel.org> Cc: linux-fscrypt@vger.kernel.org, "Theodore Y . Ts'o" <tytso@mit.edu>, Michael Halcrow <mhalcrow@google.com>, Victor Hsieh <victorhsieh@google.com>, Eric Biggers <ebiggers@google.com> Subject: [PATCH 0/2] fscrypt / f2fs: prepare I/O path for fs-verity Date: Mon, 16 Apr 2018 12:31:45 -0700 [thread overview] Message-ID: <20180416193147.104555-1-ebiggers@google.com> (raw) Hello, These two patches restructure f2fs's read path to allow the data to go through multiple postprocessing steps, rather than just decryption as is implemented currently. This is mainly in preparation for doing authenticity verification of data via fs-verity, though this change might also be useful for other future f2fs features, e.g. compression. These patches don't yet add the fs-verity work, however, as it depends on the rest of the fs-verity patchset. I'm planning to send the full patchset out as an RFC, but some parts need further investigation first. (The work-in-progress version can be found at git://git.kernel.org/pub/scm/linux/kernel/git/mhalcrow/linux.git, branch "fs-verity-dev".) Eric Biggers (2): fscrypt: allow synchronous bio decryption f2fs: refactor read path to allow multiple postprocessing steps fs/crypto/bio.c | 35 ++++--- fs/crypto/crypto.c | 8 +- fs/crypto/fscrypt_private.h | 1 - fs/ext4/readpage.c | 2 +- fs/f2fs/data.c | 163 ++++++++++++++++++++++++-------- fs/f2fs/f2fs.h | 12 ++- fs/f2fs/file.c | 4 +- fs/f2fs/gc.c | 6 +- fs/f2fs/inline.c | 2 +- fs/f2fs/super.c | 6 ++ include/linux/fscrypt_notsupp.h | 13 ++- include/linux/fscrypt_supp.h | 5 +- 12 files changed, 188 insertions(+), 69 deletions(-) -- 2.17.0.484.g0c8726318c-goog
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net> To: linux-f2fs-devel@lists.sourceforge.net, Jaegeuk Kim <jaegeuk@kernel.org> Cc: Michael Halcrow <mhalcrow@google.com>, linux-fscrypt@vger.kernel.org, "Theodore Y . Ts'o" <tytso@mit.edu>, Victor Hsieh <victorhsieh@google.com>, Eric Biggers <ebiggers@google.com> Subject: [PATCH 0/2] fscrypt / f2fs: prepare I/O path for fs-verity Date: Mon, 16 Apr 2018 12:31:45 -0700 [thread overview] Message-ID: <20180416193147.104555-1-ebiggers@google.com> (raw) Hello, These two patches restructure f2fs's read path to allow the data to go through multiple postprocessing steps, rather than just decryption as is implemented currently. This is mainly in preparation for doing authenticity verification of data via fs-verity, though this change might also be useful for other future f2fs features, e.g. compression. These patches don't yet add the fs-verity work, however, as it depends on the rest of the fs-verity patchset. I'm planning to send the full patchset out as an RFC, but some parts need further investigation first. (The work-in-progress version can be found at git://git.kernel.org/pub/scm/linux/kernel/git/mhalcrow/linux.git, branch "fs-verity-dev".) Eric Biggers (2): fscrypt: allow synchronous bio decryption f2fs: refactor read path to allow multiple postprocessing steps fs/crypto/bio.c | 35 ++++--- fs/crypto/crypto.c | 8 +- fs/crypto/fscrypt_private.h | 1 - fs/ext4/readpage.c | 2 +- fs/f2fs/data.c | 163 ++++++++++++++++++++++++-------- fs/f2fs/f2fs.h | 12 ++- fs/f2fs/file.c | 4 +- fs/f2fs/gc.c | 6 +- fs/f2fs/inline.c | 2 +- fs/f2fs/super.c | 6 ++ include/linux/fscrypt_notsupp.h | 13 ++- include/linux/fscrypt_supp.h | 5 +- 12 files changed, 188 insertions(+), 69 deletions(-) -- 2.17.0.484.g0c8726318c-goog ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next reply other threads:[~2018-04-16 19:33 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-16 19:31 Eric Biggers [this message] 2018-04-16 19:31 ` [PATCH 0/2] fscrypt / f2fs: prepare I/O path for fs-verity Eric Biggers via Linux-f2fs-devel 2018-04-16 19:31 ` [PATCH 1/2] fscrypt: allow synchronous bio decryption Eric Biggers 2018-04-16 19:31 ` Eric Biggers via Linux-f2fs-devel 2018-04-18 4:22 ` Jaegeuk Kim 2018-04-18 4:22 ` Jaegeuk Kim 2018-04-16 19:31 ` [PATCH 2/2] f2fs: refactor read path to allow multiple postprocessing steps Eric Biggers 2018-04-16 19:31 ` Eric Biggers via Linux-f2fs-devel 2018-04-16 22:15 ` Michael Halcrow 2018-04-16 22:15 ` Michael Halcrow via Linux-f2fs-devel 2018-04-17 17:31 ` Eric Biggers 2018-04-17 17:31 ` Eric Biggers via Linux-f2fs-devel 2018-04-17 9:13 ` [f2fs-dev] " Chao Yu 2018-04-17 9:13 ` Chao Yu 2018-04-17 17:42 ` [f2fs-dev] " Eric Biggers 2018-04-17 17:42 ` Eric Biggers via Linux-f2fs-devel 2018-04-18 6:27 ` [f2fs-dev] " Chao Yu 2018-04-18 6:27 ` Chao Yu 2018-04-18 17:18 ` [f2fs-dev] " Eric Biggers 2018-04-18 17:18 ` Eric Biggers via Linux-f2fs-devel 2018-04-18 17:37 ` [f2fs-dev] " Jaegeuk Kim 2018-04-18 17:37 ` Jaegeuk Kim 2018-04-19 14:41 ` [f2fs-dev] " Chao Yu 2018-04-19 14:41 ` Chao Yu
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=20180416193147.104555-1-ebiggers@google.com \ --to=ebiggers@google.com \ --cc=jaegeuk@kernel.org \ --cc=linux-f2fs-devel@lists.sourceforge.net \ --cc=linux-fscrypt@vger.kernel.org \ --cc=mhalcrow@google.com \ --cc=tytso@mit.edu \ --cc=victorhsieh@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: 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.