linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v4 1/2] IMA: Define workqueue for early boot "key" measurements
Date: Mon, 16 Dec 2019 07:30:00 -0500	[thread overview]
Message-ID: <1576499400.4579.305.camel@linux.ibm.com> (raw)
In-Reply-To: <20191213171827.28657-2-nramas@linux.microsoft.com>

On Fri, 2019-12-13 at 09:18 -0800, Lakshmi Ramasubramanian wrote:

> +/*
> + * 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);
> +	bool process = false;
> +
> +	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);
> +
> +	if (!ima_process_keys) {
> +		ima_process_keys = true;

Thank you for moving the initialization here.  The comment is now
valid and the following code is now guaranteed to execute just once.

> +
> +		if (!list_empty(&ima_keys)) {
> +			list_for_each_entry_safe(entry, tmp, &ima_keys, list)
> +				list_move_tail(&entry->list, &temp_ima_keys);
> +			process = true;
> +		}
> +	}
> +
> +	mutex_unlock(&ima_keys_mutex);
> +
> +	if (!process)
> +		return;

The new changes - checking if the list is empty and this test - are
unnecessary, as you implied earlier.

Mimi

> +
> +	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);
> +	}
> +}
> +
>  /**
>   * ima_post_key_create_or_update - measure asymmetric keys
>   * @keyring: keyring to which the key is linked to


  reply	other threads:[~2019-12-16 12:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 17:18 [PATCH v4 0/2] IMA: Deferred measurement of keys Lakshmi Ramasubramanian
2019-12-13 17:18 ` [PATCH v4 1/2] IMA: Define workqueue for early boot "key" measurements Lakshmi Ramasubramanian
2019-12-16 12:30   ` Mimi Zohar [this message]
2019-12-16 23:44     ` Lakshmi Ramasubramanian
2019-12-17 10:54       ` Mimi Zohar
2019-12-13 17:18 ` [PATCH v4 2/2] IMA: Call workqueue functions to measure queued keys Lakshmi Ramasubramanian
2019-12-13 17:25   ` James Bottomley
2019-12-13 17:31     ` Lakshmi Ramasubramanian
2019-12-15 15:22       ` James Bottomley
2019-12-16  1:12         ` Lakshmi Ramasubramanian
2019-12-16  6:53           ` James Bottomley
2019-12-16 13:05             ` Mimi Zohar
2019-12-16 19:20             ` Lakshmi Ramasubramanian
2019-12-16 21:17               ` James Bottomley
2019-12-16 21:37                 ` Lakshmi Ramasubramanian
2019-12-16 21:52                   ` Lakshmi Ramasubramanian
2019-12-17 22:22                     ` Lakshmi Ramasubramanian
2019-12-18  2:01                       ` James Bottomley
2019-12-18  2:44                         ` Lakshmi Ramasubramanian
2019-12-18  3:00                           ` Lakshmi Ramasubramanian
2019-12-18  3:24                             ` James Bottomley

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=1576499400.4579.305.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).