[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1574299330.4793.158.camel@linux.ibm.com>
Date: Wed, 20 Nov 2019 20:22:10 -0500
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Lakshmi Ramasubramanian <nramas@...ux.microsoft.com>,
Eric Snowberg <eric.snowberg@...cle.com>
Cc: linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
keyrings@...r.kernel.org
Subject: Re: [PATCH v8 2/5] IMA: Define an IMA hook to measure keys
On Wed, 2019-11-20 at 15:40 -0800, Lakshmi Ramasubramanian wrote:
> On 11/20/2019 3:28 PM, Eric Snowberg wrote:
> Hi Eric,
>
> >
> > I’m interested in using this patch series, however I get the following on every boot:
>
> > [ 1.222749] Call Trace:
> > [ 1.223344] ? crypto_destroy_tfm+0x5f/0xb0
> > [ 1.224315] ima_get_action+0x2c/0x30
> > [ 1.225148] process_buffer_measurement+0x1da/0x230
> > [ 1.226306] ima_post_key_create_or_update+0x3b/0x40
>
> This is happening because IMA is not yet initialized when the IMA hook
> is called.
>
> I had the following check in process_buffer_measurement() as part of my
> patch, but removed it since it is being upstreamed separately (by Mimi)
>
> if (!ima_policy_flag)
> return;
Did you post it as a separate patch? I can't seem to find it.
Mimi
>
> Until this change is in, please add the above line locally on entry to
> process_buffer_measurement() to get around the issue.
>
> thanks,
> -lakshmi
Powered by blists - more mailing lists