From: Mimi Zohar <zohar@linux.ibm.com>
To: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-integrity@vger.kernel.org
Cc: sashal@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IMA: Turn IMA_MEASURE_ASYMMETRIC_KEYS off by default
Date: Wed, 22 Jan 2020 15:54:58 -0500 [thread overview]
Message-ID: <1579726498.4644.4.camel@linux.ibm.com> (raw)
In-Reply-To: <fa7ec770-6552-7538-7393-c23410b3a1ba@linux.microsoft.com>
On Wed, 2020-01-22 at 12:05 -0800, Lakshmi Ramasubramanian wrote:
> On 1/22/20 12:02 PM, Mimi Zohar wrote:
>
> >
> > Thanks, Lakshmi. This requires moving the code around. Instead of
> > doing this on the current code base, I suggest posting a v9 version of
> > the entire "IMA: Deferred measurement of keys".
> >
> > I suggest making the switch from spinlock to mutex, as you had it
> > originally, before posting v9. The commit history will then be a lot
> > cleaner.
> >
> > thanks,
> >
> > Mimi
> >
>
> Sure Mimi - I'll post an update to the patch set shortly.
I just pushed out the next-integrity-testing branch without the
"Deferred measurement of keys" patches. I've kept the "IMA: pre-
allocate buffer to hold keyrings string" patch, though it probably
isn't required.
thanks,
Mimi
next prev parent reply other threads:[~2020-01-22 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 17:13 [PATCH] IMA: Turn IMA_MEASURE_ASYMMETRIC_KEYS off by default Lakshmi Ramasubramanian
2020-01-21 17:34 ` James Bottomley
2020-01-21 18:00 ` Lakshmi Ramasubramanian
2020-01-21 19:13 ` Mimi Zohar
2020-01-21 19:52 ` James Bottomley
2020-01-21 20:38 ` Lakshmi Ramasubramanian
2020-01-22 20:02 ` Mimi Zohar
2020-01-22 20:05 ` Lakshmi Ramasubramanian
2020-01-22 20:54 ` Mimi Zohar [this message]
2020-01-22 12:23 ` 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=1579726498.4644.4.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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