Re: [PATCH v7 0/3] LoadPin: Enable loading from trusted dm-verity devices

From: Kees Cook <keescook@chromium.org>
To: jmorris@namei.org, agk@redhat.com, snitzer@kernel.org,
	mka@chromium.org, serge@hallyn.com
Cc: Kees Cook <keescook@chromium.org>,
	linux-raid@vger.kernel.org, song@kernel.org,
	dianders@chromium.org, linux-security-module@vger.kernel.org,
	dm-devel@redhat.com, gmazyland@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/3] LoadPin: Enable loading from trusted dm-verity devices
Date: Fri,  8 Jul 2022 10:47:59 -0700	[thread overview]
Message-ID: <165730247648.3882109.12888837825450019581.b4-ty@chromium.org> (raw)
In-Reply-To: <20220627153526.3750341-1-mka@chromium.org>

On Mon, 27 Jun 2022 08:35:23 -0700, Matthias Kaehlcke wrote:
> As of now LoadPin restricts loading of kernel files to a single pinned
> filesystem, typically the rootfs. This works for many systems, however it
> can result in a bloated rootfs (and OTA updates) on platforms where
> multiple boards with different hardware configurations use the same rootfs
> image. Especially when 'optional' files are large it may be preferable to
> download/install them only when they are actually needed by a given board.
> Chrome OS uses Downloadable Content (DLC) [1] to deploy certain 'packages'
> at runtime. As an example a DLC package could contain firmware for a
> peripheral that is not present on all boards. DLCs use dm-verity [2] to
> verify the integrity of the DLC content.
> 
> [...]

Applied to for-next/hardening, thanks!

[1/3] dm: Add verity helpers for LoadPin
      https://git.kernel.org/kees/c/b6c1c5745ccc
[2/3] LoadPin: Enable loading from trusted dm-verity devices
      https://git.kernel.org/kees/c/3f805f8cc23b
[3/3] dm: verity-loadpin: Use CONFIG_SECURITY_LOADPIN_VERITY for conditional compilation
      https://git.kernel.org/kees/c/231af4709018

-- 
Kees Cook