[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1578437512.5222.110.camel@linux.ibm.com>
Date: Tue, 07 Jan 2020 17:51:52 -0500
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Lakshmi Ramasubramanian <nramas@...ux.microsoft.com>,
James.Bottomley@...senPartnership.com,
linux-integrity@...r.kernel.org
Cc: eric.snowberg@...cle.com, dhowells@...hat.com,
mathew.j.martineau@...ux.intel.com, matthewgarrett@...gle.com,
sashal@...nel.org, jamorris@...ux.microsoft.com,
linux-kernel@...r.kernel.org, keyrings@...r.kernel.org
Subject: Re: [PATCH 2/4] KEYS: Call the IMA hook to measure keys
On Tue, 2020-01-07 at 11:43 -0800, Lakshmi Ramasubramanian wrote:
> Call the IMA hook from key_create_or_update() function to measure
> the payload when a new key is created or an existing key is updated.
>
> This patch adds the call to the IMA hook from key_create_or_update()
> function to measure the key on key create or update.
>
> Signed-off-by: Lakshmi Ramasubramanian <nramas@...ux.microsoft.com>
> Cc: David Howells <dhowells@...hat.com>
> Cc: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
> Reported-by: kbuild test robot <lkp@...el.com> # ima_asymmetric_keys.c
> is built as a kernel module when it is actually not.
> Fixes: cb1aa3823c92 ("KEYS: Call the IMA hook to measure keys")
There are two ways of addressing a bug report. One is by fixing the
original patch, while the other addresses the bug as a separate patch.
If the fix is squashed into the original patch, the commit number
will change. Only if the fix is a separate patch, would you include
the "Fixes" tag.
Mimi
Powered by blists - more mailing lists