From: Alexander Larsson <alexl@redhat.com>
To: miklos@szeredi.hu
Cc: linux-unionfs@vger.kernel.org, amir73il@gmail.com,
ebiggers@kernel.org, tytso@mit.edu, fsverity@lists.linux.dev,
Alexander Larsson <alexl@redhat.com>
Subject: [PATCH 0/6] ovl: Add support for fs-verity checking of lowerdata
Date: Thu, 20 Apr 2023 09:43:59 +0200 [thread overview]
Message-ID: <cover.1681917551.git.alexl@redhat.com> (raw)
This patchset adds support for using fs-verity to validate lowerdata
files by specifying an overlay.verity xattr on the metacopy
files.
This is primarily motivated by the Composefs usecase, where there will
be a read-only EROFS layer that contains redirect into a base data
layer which has fs-verity enabled on all files. However, it is also
useful in general if you want to ensure that the lowerdata files
matches the expected content over time.
This patch series is based on the lazy lowerdata patch series by Amir[1].
I have also added some tests for this feature to xfstests[2].
I'm also CC:ing the fsverity list and maintainers because there is one
(tiny) fsverity change, and there may be interest in this usecase.
[1] https://lore.kernel.org/linux-unionfs/20230412135412.1684197-1-amir73il@gmail.com/T/#m1bc31eb75dc9dd22204b8f0cfc67bad9b6c785a7
[2] https://github.com/alexlarsson/xfstests/commits/verity-tests
Alexander Larsson (6):
fsverity: Export fsverity_get_digest
ovl: Break out ovl_entry_path_real() from ovl_i_path_real()
ovl: Break out ovl_entry_path_lowerdata() from ovl_path_lowerdata()
ovl: Add framework for verity support
ovl: Validate verity xattr when resolving lowerdata
ovl: Handle verity during copy-up
Documentation/filesystems/overlayfs.rst | 33 +++++
fs/overlayfs/Kconfig | 14 ++
fs/overlayfs/copy_up.c | 27 ++++
fs/overlayfs/namei.c | 34 +++++
fs/overlayfs/overlayfs.h | 11 ++
fs/overlayfs/ovl_entry.h | 4 +
fs/overlayfs/super.c | 49 +++++++
fs/overlayfs/util.c | 167 ++++++++++++++++++++++--
fs/verity/measure.c | 1 +
9 files changed, 332 insertions(+), 8 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-20 7:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 7:43 Alexander Larsson [this message]
2023-04-20 7:44 ` [PATCH 1/6] fsverity: Export fsverity_get_digest Alexander Larsson
2023-04-20 7:44 ` [PATCH 2/6] ovl: Break out ovl_entry_path_real() from ovl_i_path_real() Alexander Larsson
2023-04-20 12:12 ` Amir Goldstein
2023-04-20 7:44 ` [PATCH 3/6] ovl: Break out ovl_entry_path_lowerdata() from ovl_path_lowerdata() Alexander Larsson
2023-04-20 12:14 ` Amir Goldstein
2023-04-20 7:44 ` [PATCH 4/6] ovl: Add framework for verity support Alexander Larsson
2023-04-20 8:39 ` Amir Goldstein
2023-04-25 11:19 ` Miklos Szeredi
2023-04-25 13:33 ` Alexander Larsson
2023-04-25 19:07 ` Miklos Szeredi
2023-04-20 7:44 ` [PATCH 5/6] ovl: Validate verity xattr when resolving lowerdata Alexander Larsson
2023-04-20 12:06 ` Amir Goldstein
2023-04-27 7:33 ` Alexander Larsson
2023-04-26 21:47 ` Eric Biggers
2023-04-27 7:22 ` Alexander Larsson
2023-04-27 17:58 ` Eric Biggers
2023-04-20 7:44 ` [PATCH 6/6] ovl: Handle verity during copy-up Alexander Larsson
2023-04-20 12:17 ` Amir Goldstein
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=cover.1681917551.git.alexl@redhat.com \
--to=alexl@redhat.com \
--cc=amir73il@gmail.com \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).