From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Kees Cook <keescook@chromium.org>,
James Morris <jmorris@namei.org>,
"Serge E . Hallyn" <serge@hallyn.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, dm-devel@redhat.com,
linux-raid@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Song Liu <song@kernel.org>
Subject: Re: [PATCH v2 0/3] LoadPin: Enable loading from trusted dm-verity devices
Date: Thu, 28 Apr 2022 07:32:44 +0200 [thread overview]
Message-ID: <e5aa84ee-69b3-b02a-014d-597a5a03987d@molgen.mpg.de> (raw)
In-Reply-To: <20220426213110.3572568-1-mka@chromium.org>
Dear Matthias,
Thank you for your patches.
Am 26.04.22 um 23:31 schrieb Matthias Kaehlcke:
> As of now LoadPin restricts loading of kernel files to a single
> pinned filesystem, typically the rootfs. This works for many
[…]
A small nit, if you should reroll the patches, please use 75 characters
per line in commit messages. (`scripts/checkpatch.pl` uses that number.)
Kind regards,
Paul
prev parent reply other threads:[~2022-04-28 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 21:31 [PATCH v2 0/3] LoadPin: Enable loading from trusted dm-verity devices Matthias Kaehlcke
2022-04-26 21:31 ` [PATCH v2 1/3] dm: Add verity helpers for LoadPin Matthias Kaehlcke
2022-04-26 21:31 ` [PATCH v2 2/3] LoadPin: Enable loading from trusted dm-verity devices Matthias Kaehlcke
2022-04-27 16:06 ` kernel test robot
2022-04-28 1:59 ` kernel test robot
2022-05-01 6:21 ` Kees Cook
2022-05-02 22:44 ` Matthias Kaehlcke
2022-04-26 21:31 ` [PATCH v2 3/3] dm: verity-loadpin: Use CONFIG_SECURITY_LOADPIN_VERITY for conditional compilation Matthias Kaehlcke
2022-04-28 5:32 ` Paul Menzel [this message]
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=e5aa84ee-69b3-b02a-014d-597a5a03987d@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=agk@redhat.com \
--cc=dianders@chromium.org \
--cc=dm-devel@redhat.com \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mka@chromium.org \
--cc=serge@hallyn.com \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
/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).