From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org, jarkko.sakkinen@linux.intel.com
Cc: jgg@ziepe.ca, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] ima: Use tpm_chip_find() and access TPM functions using it
Date: Thu, 21 Jun 2018 16:53:45 -0400 [thread overview]
Message-ID: <1529614425.23843.20.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180620204236.1572523-4-stefanb@linux.vnet.ibm.com>
On Wed, 2018-06-20 at 16:42 -0400, Stefan Berger wrote:
> Rather than accessing the TPM functions using a NULL pointer, which
> causes a lookup for a suitable chip every time, get a hold of a tpm_chip
> and access the TPM functions using this chip. We call the tpm_chip
> ima_tpm_chip and protect it, once initialization is done, using a
> rw_semaphore called ima_tpm_chip_lock.
>
> Use ima_shutdown to release the tpm_chip.
>
> Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
> ---
> security/integrity/ima/ima.h | 3 +++
> security/integrity/ima/ima_crypto.c | 12 ++++++++++--
> security/integrity/ima/ima_init.c | 19 ++++++++++++-------
> security/integrity/ima/ima_queue.c | 7 +++++--
> 4 files changed, 30 insertions(+), 11 deletions(-)
>
> diff --git a/security/integrity/ima/ima.h b/security/integrity/ima/ima.h
> index 354bb5716ce3..53a88d578ca5 100644
> --- a/security/integrity/ima/ima.h
> +++ b/security/integrity/ima/ima.h
> @@ -24,6 +24,7 @@
> #include <linux/hash.h>
> #include <linux/tpm.h>
> #include <linux/audit.h>
> +#include <linux/rwsem.h>
> #include <crypto/hash_info.h>
>
> #include "../integrity.h"
> @@ -56,6 +57,8 @@ extern int ima_policy_flag;
> extern int ima_used_chip;
> extern int ima_hash_algo;
> extern int ima_appraise;
> +extern struct rw_semaphore ima_tpm_chip_lock;
> +extern struct tpm_chip *ima_tpm_chip;
ima_add_templatE_entry() synchronizes appending a measurement to the
measurement list and extending the TPM by taking a lock. Do we really
need to introduce another lock?
Mimi
>
> /* IMA event related data */
> struct ima_event_data {
> diff --git a/security/integrity/ima/ima_crypto.c b/security/integrity/ima/ima_crypto.c
> index 4e085a17124f..da7715240476 100644
> --- a/security/integrity/ima/ima_crypto.c
> +++ b/security/integrity/ima/ima_crypto.c
> @@ -631,10 +631,18 @@ int ima_calc_buffer_hash(const void *buf, loff_t len,
>
> static void __init ima_pcrread(int idx, u8 *pcr)
> {
> + int result = 0;
> +
> + down_read(&ima_tpm_chip_lock);
> +
> if (!ima_used_chip)
> - return;
> + goto out;
> +
> + result = tpm_pcr_read(ima_tpm_chip, idx, pcr);
> +out:
> + up_read(&ima_tpm_chip_lock);
>
> - if (tpm_pcr_read(NULL, idx, pcr) != 0)
> + if (result != 0)
> pr_err("Error Communicating to TPM chip\n");
> }
>
> diff --git a/security/integrity/ima/ima_init.c b/security/integrity/ima/ima_init.c
> index 8a5258eb32b6..24db06c4f463 100644
> --- a/security/integrity/ima/ima_init.c
> +++ b/security/integrity/ima/ima_init.c
> @@ -28,6 +28,8 @@
> /* name for boot aggregate entry */
> static const char *boot_aggregate_name = "boot_aggregate";
> int ima_used_chip;
> +struct rw_semaphore ima_tpm_chip_lock = __RWSEM_INITIALIZER(ima_tpm_chip_lock);
> +struct tpm_chip *ima_tpm_chip;
>
> /* Add the boot aggregate to the IMA measurement list and extend
> * the PCR register.
> @@ -108,6 +110,13 @@ void __init ima_load_x509(void)
> static int ima_shutdown(struct notifier_block *this, unsigned long action,
> void *data)
> {
> + down_write(&ima_tpm_chip_lock);
> + if (ima_tpm_chip) {
> + tpm_chip_put(ima_tpm_chip);
> + ima_tpm_chip = NULL;
> + ima_used_chip = 0;
> + }
> + up_write(&ima_tpm_chip_lock);
> return NOTIFY_DONE;
> }
>
> @@ -118,19 +127,15 @@ static struct notifier_block ima_reboot_notifier = {
>
> int __init ima_init(void)
> {
> - u8 pcr_i[TPM_DIGEST_SIZE];
> int rc;
>
> register_reboot_notifier(&ima_reboot_notifier);
>
> - ima_used_chip = 0;
> - rc = tpm_pcr_read(NULL, 0, pcr_i);
> - if (rc == 0)
> - ima_used_chip = 1;
> + ima_tpm_chip = tpm_chip_find();
>
> + ima_used_chip = (ima_tpm_chip != NULL);
> if (!ima_used_chip)
> - pr_info("No TPM chip found, activating TPM-bypass! (rc=%d)\n",
> - rc);
> + pr_info("No TPM chip found, activating TPM-bypass!\n");
>
> rc = integrity_init_keyring(INTEGRITY_KEYRING_IMA);
> if (rc)
> diff --git a/security/integrity/ima/ima_queue.c b/security/integrity/ima/ima_queue.c
> index 418f35e38015..6c9427939a28 100644
> --- a/security/integrity/ima/ima_queue.c
> +++ b/security/integrity/ima/ima_queue.c
> @@ -142,10 +142,13 @@ static int ima_pcr_extend(const u8 *hash, int pcr)
> {
> int result = 0;
>
> + down_read(&ima_tpm_chip_lock);
> if (!ima_used_chip)
> - return result;
> + goto out;
>
> - result = tpm_pcr_extend(NULL, pcr, hash);
> + result = tpm_pcr_extend(ima_tpm_chip, pcr, hash);
> +out:
> + up_read(&ima_tpm_chip_lock);
> if (result != 0)
> pr_err("Error Communicating to TPM chip, result: %d\n", result);
> return result;
next prev parent reply other threads:[~2018-06-21 20:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 20:42 [PATCH v2 0/4] Have IMA find and use a tpm_chip until system shutdown Stefan Berger
2018-06-20 20:42 ` [PATCH v2 1/4] tpm: Implement tpm_chip_find() and tpm_chip_put() for other subsystems Stefan Berger
2018-06-20 20:50 ` Jason Gunthorpe
2018-06-20 21:13 ` Stefan Berger
2018-06-21 17:13 ` Jarkko Sakkinen
2018-06-21 17:15 ` Jarkko Sakkinen
2018-06-21 17:27 ` Stefan Berger
2018-06-21 17:45 ` Stefan Berger
2018-06-21 17:56 ` Jason Gunthorpe
2018-06-21 18:19 ` Stefan Berger
2018-06-21 19:06 ` Jason Gunthorpe
2018-06-21 20:14 ` Stefan Berger
2018-06-21 20:51 ` Jason Gunthorpe
2018-06-20 20:42 ` [PATCH v2 2/4] ima: Implement ima_shutdown and register it as a reboot_notifier Stefan Berger
2018-06-20 20:42 ` [PATCH v2 3/4] ima: Use tpm_chip_find() and access TPM functions using it Stefan Berger
2018-06-21 20:53 ` Mimi Zohar [this message]
2018-06-21 20:59 ` Stefan Berger
2018-06-22 3:25 ` Jason Gunthorpe
2018-06-22 11:40 ` Stefan Berger
2018-06-22 14:19 ` Jason Gunthorpe
2018-06-20 20:42 ` [PATCH v2 4/4] ima: Get rid of ima_used_chip and use ima_tpm_chip != NULL instead Stefan Berger
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=1529614425.23843.20.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanb@linux.vnet.ibm.com \
/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