From: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>
To: Mimi Zohar <zohar@linux.ibm.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 18:59:39 -0800 [thread overview]
Message-ID: <c60341a3-2329-cd92-c76c-6f8249a57b43@linux.microsoft.com> (raw)
In-Reply-To: <1576204377.4579.206.camel@linux.ibm.com>
On 12/12/2019 6:32 PM, Mimi Zohar wrote:
>>>
>>> Don't you need a test here, before setting ima_process_keys?
>>>
>>> if (ima_process_keys)
>>> return;
>>>
>>> Mimi
>>
>> That check is done before the comment - at the start of
>> ima_process_queued_keys().
>
> The first test prevents taking the mutex unnecessarily.
>
> Mimi
I am trying to understand your concern here. Could you please clarify?
=> If ima_process_keys is false
-> With the mutex held, should check ima_process_keys again
before setting?
Let's say 2 or more threads are racing in calling ima_process_queued_keys():
The 1st one will set ima_process_keys and process queued keys.
The 2nd and subsequent ones - even if they have gone past the initial
check, will find an empty list of keys (the list "ima_keys") when they
take the mutex. So they'll not process any keys.
thanks,
-lakshmi
next prev parent reply other threads:[~2019-12-13 2:59 UTC|newest]
Thread overview: 10+ 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 ` [PATCH v3 1/2] IMA: Define workqueue for early boot "key" measurements Lakshmi Ramasubramanian
2019-12-13 1:55 ` Mimi Zohar
2019-12-13 1:59 ` Lakshmi Ramasubramanian
2019-12-13 2:32 ` Mimi Zohar
2019-12-13 2:59 ` Lakshmi Ramasubramanian [this message]
2019-12-13 13:06 ` Mimi Zohar
2019-12-13 15:51 ` Lakshmi Ramasubramanian
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
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=c60341a3-2329-cd92-c76c-6f8249a57b43@linux.microsoft.com \
--to=nramas@linux.microsoft.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=sashal@kernel.org \
--cc=zohar@linux.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