On Fri, 2 Oct 2020, Kees Cook wrote:
> FIRMWARE_PREALLOC_BUFFER is a "how", not a "what", and confuses the LSMs
> that are interested in filtering between types of things. The "how"
> should be an internal detail made uninteresting to the LSMs.
>
> Fixes: a098ecd2fa7d ("firmware: support loading into a pre-allocated buffer")
> Fixes: fd90bc559bfb ("ima: based on policy verify firmware signatures
> (pre-allocated buffer)")
> Fixes: 4f0496d8ffa3 ("ima: based on policy warn about loading firmware
> (pre-allocated buffer)")
> Signed-off-by: Kees Cook <keesc...@chromium.org>
> Reviewed-by: Mimi Zohar <zo...@linux.ibm.com>
> Reviewed-by: Luis Chamberlain <mcg...@kernel.org>
> Acked-by: Scott Branden <scott.bran...@broadcom.com>
> Cc: sta...@vger.kernel.org
Reviewed-by: James Morris <jamor...@linux.microsoft.com>
--
James Morris
<jmor...@namei.org>
