[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1547566455.4156.283.camel@linux.ibm.com>
Date: Tue, 15 Jan 2019 10:34:15 -0500
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Kairui Song <kasong@...hat.com>, linux-kernel@...r.kernel.org
Cc: dhowells@...hat.com, dwmw2@...radead.org,
jwboyer@...oraproject.org, keyrings@...r.kernel.org,
jmorris@...ei.org, serge@...lyn.com, bauerman@...ux.ibm.com,
ebiggers@...gle.com, nayna@...ux.ibm.com, dyoung@...hat.com,
linux-integrity@...r.kernel.org, kexec@...ts.infradead.org
Subject: Re: [RFC PATCH v2 1/2] integrity, KEYS: add a reference to platform
keyring
On Tue, 2019-01-15 at 17:45 +0800, Kairui Song wrote:
[snip]
> diff --git a/security/integrity/digsig.c b/security/integrity/digsig.c
> index f45d6edecf99..bfabc2a8111d 100644
> --- a/security/integrity/digsig.c
> +++ b/security/integrity/digsig.c
> @@ -89,6 +89,12 @@ static int __integrity_init_keyring(const unsigned int id, key_perm_t perm,
> keyring[id] = NULL;
> }
>
> +#ifdef CONFIG_INTEGRITY_PLATFORM_KEYRING
> + if (id == INTEGRITY_KEYRING_PLATFORM) {
> + set_platform_trusted_keys(keyring[id]);
> + }
> +#endif
> +
> return err;
> }
>
Any reason for setting it here as opposed to in the caller
platform_keyring_init()?
Mimi
Powered by blists - more mailing lists