From: Mimi Zohar <zohar@linux.ibm.com>
To: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
linux-integrity@vger.kernel.org
Cc: eric.snowberg@oracle.com, dhowells@redhat.com,
mathew.j.martineau@linux.intel.com, matthewgarrett@google.com,
sashal@kernel.org, jamorris@linux.microsoft.com,
linux-kernel@vger.kernel.org, keyrings@vger.kernel.org
Subject: Re: [PATCH v3 1/2] IMA: Define workqueue for early boot "key" measurements
Date: Fri, 13 Dec 2019 01:55:34 +0000 [thread overview]
Message-ID: <1576202134.4579.189.camel@linux.ibm.com> (raw)
In-Reply-To: <20191213004250.21132-2-nramas@linux.microsoft.com>
> +/*
> + * ima_process_queued_keys() - process keys queued for measurement
> + *
> + * This function sets ima_process_keys to true and processes queued keys.
> + * From here on keys will be processed right away (not queued).
> + */
> +void ima_process_queued_keys(void)
> +{
> + struct ima_key_entry *entry, *tmp;
> + LIST_HEAD(temp_ima_keys);
> +
> + if (ima_process_keys)
> + return;
> +
> + /*
> + * To avoid holding the mutex when processing queued keys,
> + * transfer the queued keys with the mutex held to a temp list,
> + * release the mutex, and then process the queued keys from
> + * the temp list.
> + *
> + * Since ima_process_keys is set to true, any new key will be
> + * processed immediately and not be queued.
> + */
> + INIT_LIST_HEAD(&temp_ima_keys);
> +
> + mutex_lock(&ima_keys_mutex);
Don't you need a test here, before setting ima_process_keys?
if (ima_process_keys)
return;
Mimi
> +
> + ima_process_keys = true;
> +
> + list_for_each_entry_safe(entry, tmp, &ima_keys, list)
> + list_move_tail(&entry->list, &temp_ima_keys);
> +
> + mutex_unlock(&ima_keys_mutex);
> +
> + list_for_each_entry_safe(entry, tmp, &temp_ima_keys, list) {
> + process_buffer_measurement(entry->payload, entry->payload_len,
> + entry->keyring_name, KEY_CHECK, 0,
> + entry->keyring_name);
> + list_del(&entry->list);
> + ima_free_key_entry(entry);
> + }
> +}
> +
>
WARNING: multiple messages have this Message-ID (diff)
From: Mimi Zohar <zohar@linux.ibm.com>
To: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
linux-integrity@vger.kernel.org
Cc: eric.snowberg@oracle.com, dhowells@redhat.com,
mathew.j.martineau@linux.intel.com, matthewgarrett@google.com,
sashal@kernel.org, jamorris@linux.microsoft.com,
linux-kernel@vger.kernel.org, keyrings@vger.kernel.org
Subject: Re: [PATCH v3 1/2] IMA: Define workqueue for early boot "key" measurements
Date: Thu, 12 Dec 2019 20:55:34 -0500 [thread overview]
Message-ID: <1576202134.4579.189.camel@linux.ibm.com> (raw)
In-Reply-To: <20191213004250.21132-2-nramas@linux.microsoft.com>
> +/*
> + * ima_process_queued_keys() - process keys queued for measurement
> + *
> + * This function sets ima_process_keys to true and processes queued keys.
> + * From here on keys will be processed right away (not queued).
> + */
> +void ima_process_queued_keys(void)
> +{
> + struct ima_key_entry *entry, *tmp;
> + LIST_HEAD(temp_ima_keys);
> +
> + if (ima_process_keys)
> + return;
> +
> + /*
> + * To avoid holding the mutex when processing queued keys,
> + * transfer the queued keys with the mutex held to a temp list,
> + * release the mutex, and then process the queued keys from
> + * the temp list.
> + *
> + * Since ima_process_keys is set to true, any new key will be
> + * processed immediately and not be queued.
> + */
> + INIT_LIST_HEAD(&temp_ima_keys);
> +
> + mutex_lock(&ima_keys_mutex);
Don't you need a test here, before setting ima_process_keys?
if (ima_process_keys)
return;
Mimi
> +
> + ima_process_keys = true;
> +
> + list_for_each_entry_safe(entry, tmp, &ima_keys, list)
> + list_move_tail(&entry->list, &temp_ima_keys);
> +
> + mutex_unlock(&ima_keys_mutex);
> +
> + list_for_each_entry_safe(entry, tmp, &temp_ima_keys, list) {
> + process_buffer_measurement(entry->payload, entry->payload_len,
> + entry->keyring_name, KEY_CHECK, 0,
> + entry->keyring_name);
> + list_del(&entry->list);
> + ima_free_key_entry(entry);
> + }
> +}
> +
>
next prev parent reply other threads:[~2019-12-13 1:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 0:42 [PATCH v3 0/2] IMA: Deferred measurement of keys Lakshmi Ramasubramanian
2019-12-13 0:42 ` Lakshmi Ramasubramanian
2019-12-13 0:42 ` [PATCH v3 1/2] IMA: Define workqueue for early boot "key" measurements Lakshmi Ramasubramanian
2019-12-13 0:42 ` Lakshmi Ramasubramanian
2019-12-13 1:55 ` Mimi Zohar [this message]
2019-12-13 1:55 ` Mimi Zohar
2019-12-13 1:59 ` Lakshmi Ramasubramanian
2019-12-13 1:59 ` Lakshmi Ramasubramanian
2019-12-13 2:32 ` Mimi Zohar
2019-12-13 2:32 ` Mimi Zohar
2019-12-13 2:59 ` Lakshmi Ramasubramanian
2019-12-13 2:59 ` Lakshmi Ramasubramanian
2019-12-13 13:06 ` Mimi Zohar
2019-12-13 13:06 ` Mimi Zohar
2019-12-13 15:51 ` Lakshmi Ramasubramanian
2019-12-13 15:51 ` Lakshmi Ramasubramanian
2019-12-15 12:44 ` Mimi Zohar
2019-12-15 12:44 ` Mimi Zohar
2019-12-13 0:42 ` [PATCH v3 2/2] IMA: Call workqueue functions to measure queued keys Lakshmi Ramasubramanian
2019-12-13 0:42 ` Lakshmi Ramasubramanian
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=1576202134.4579.189.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=dhowells@redhat.com \
--cc=eric.snowberg@oracle.com \
--cc=jamorris@linux.microsoft.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthewgarrett@google.com \
--cc=nramas@linux.microsoft.com \
--cc=sashal@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.