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 v1 1/2] IMA: Define workqueue for early boot "key" measurements
Date: Wed, 11 Dec 2019 13:04:02 +0000 [thread overview]
Message-ID: <1576069442.4579.131.camel@linux.ibm.com> (raw)
In-Reply-To: <1576028407.4579.77.camel@linux.ibm.com>
On Tue, 2019-12-10 at 20:40 -0500, Mimi Zohar wrote:
> > +void ima_process_queued_keys_for_measurement(void)
> > +{
> > + struct ima_measure_key_entry *entry, *tmp;
> > + LIST_HEAD(temp_ima_measure_keys);
> > +
> > + if (ima_process_keys_for_measurement)
> > + return;
> > +
> > + /*
> > + * Any queued keys will be processed now. From here on
> > + * keys should be processed right away.
> > + */
> > + ima_process_keys_for_measurement = true;
>
> This function and the ima_queue_key_for_measurement() are not
> exported, so don't require kernel-doc style comments, but at least
> this comment should not be here. It could be included as part of the
> function description at the head of the function.
Sorry, one more comment. Appending "_for_measurement" or inserting
"_measure_" makes these function names unnecessarily long. This
information can be included in the function descriptions.
Mimi
>
> Remember we don't add code comments needlessly. Refer to section "8)
> Commenting" in Documentation/process/coding-style.rst.
>
> > +
> > + /*
> > + * 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_for_measurement is set to true above,
> > + * any new key will be processed immediately and not be queued.
> > + */
> > + INIT_LIST_HEAD(&temp_ima_measure_keys);
> > +
> > + mutex_lock(&ima_measure_keys_mutex);
> > +
> > + list_for_each_entry_safe(entry, tmp, &ima_measure_keys, list)
> > + list_move_tail(&entry->list, &temp_ima_measure_keys);
> > +
> > + mutex_unlock(&ima_measure_keys_mutex);
> > +
> > + list_for_each_entry_safe(entry, tmp, &temp_ima_measure_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_measure_key_entry(entry);
> > + }
> > +}
> > +
> > /**
> > * ima_post_key_create_or_update - measure asymmetric keys
> > * @keyring: keyring to which the key is linked to
>
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 v1 1/2] IMA: Define workqueue for early boot "key" measurements
Date: Wed, 11 Dec 2019 08:04:02 -0500 [thread overview]
Message-ID: <1576069442.4579.131.camel@linux.ibm.com> (raw)
In-Reply-To: <1576028407.4579.77.camel@linux.ibm.com>
On Tue, 2019-12-10 at 20:40 -0500, Mimi Zohar wrote:
> > +void ima_process_queued_keys_for_measurement(void)
> > +{
> > + struct ima_measure_key_entry *entry, *tmp;
> > + LIST_HEAD(temp_ima_measure_keys);
> > +
> > + if (ima_process_keys_for_measurement)
> > + return;
> > +
> > + /*
> > + * Any queued keys will be processed now. From here on
> > + * keys should be processed right away.
> > + */
> > + ima_process_keys_for_measurement = true;
>
> This function and the ima_queue_key_for_measurement() are not
> exported, so don't require kernel-doc style comments, but at least
> this comment should not be here. It could be included as part of the
> function description at the head of the function.
Sorry, one more comment. Appending "_for_measurement" or inserting
"_measure_" makes these function names unnecessarily long. This
information can be included in the function descriptions.
Mimi
>
> Remember we don't add code comments needlessly. Refer to section "8)
> Commenting" in Documentation/process/coding-style.rst.
>
> > +
> > + /*
> > + * 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_for_measurement is set to true above,
> > + * any new key will be processed immediately and not be queued.
> > + */
> > + INIT_LIST_HEAD(&temp_ima_measure_keys);
> > +
> > + mutex_lock(&ima_measure_keys_mutex);
> > +
> > + list_for_each_entry_safe(entry, tmp, &ima_measure_keys, list)
> > + list_move_tail(&entry->list, &temp_ima_measure_keys);
> > +
> > + mutex_unlock(&ima_measure_keys_mutex);
> > +
> > + list_for_each_entry_safe(entry, tmp, &temp_ima_measure_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_measure_key_entry(entry);
> > + }
> > +}
> > +
> > /**
> > * ima_post_key_create_or_update - measure asymmetric keys
> > * @keyring: keyring to which the key is linked to
>
next prev parent reply other threads:[~2019-12-11 13:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 1:29 [PATCH v1 0/2] IMA: Deferred measurement of keys Lakshmi Ramasubramanian
2019-12-06 1:29 ` Lakshmi Ramasubramanian
2019-12-06 1:29 ` [PATCH v1 1/2] IMA: Define workqueue for early boot "key" measurements Lakshmi Ramasubramanian
2019-12-06 1:29 ` Lakshmi Ramasubramanian
2019-12-11 1:40 ` Mimi Zohar
2019-12-11 1:40 ` Mimi Zohar
2019-12-11 13:04 ` Mimi Zohar [this message]
2019-12-11 13:04 ` Mimi Zohar
2019-12-11 18:58 ` Lakshmi Ramasubramanian
2019-12-06 1:29 ` [PATCH v1 2/2] IMA: Call workqueue functions to measure queued keys Lakshmi Ramasubramanian
2019-12-06 1:29 ` Lakshmi Ramasubramanian
2019-12-11 1:40 ` Mimi Zohar
2019-12-11 1:40 ` Mimi Zohar
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=1576069442.4579.131.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.