From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1,USER_IN_DEF_DKIM_WL autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 37D91C432C0 for ; Wed, 20 Nov 2019 23:39:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1072D208A1 for ; Wed, 20 Nov 2019 23:39:56 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=linux.microsoft.com header.i=@linux.microsoft.com header.b="GwkKe1t8" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725936AbfKTXjw (ORCPT ); Wed, 20 Nov 2019 18:39:52 -0500 Received: from linux.microsoft.com ([13.77.154.182]:52866 "EHLO linux.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725878AbfKTXjw (ORCPT ); Wed, 20 Nov 2019 18:39:52 -0500 Received: from [10.137.112.111] (unknown [131.107.147.111]) by linux.microsoft.com (Postfix) with ESMTPSA id 7CE8420B7185; Wed, 20 Nov 2019 15:39:51 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 7CE8420B7185 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1574293191; bh=fBnSdarksQEg07LJd/+YN30Ehp+o/3EE9sMPeU4CzwY=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=GwkKe1t8XcQy5/t9J/I76+iHZbWRwe/ShA4SV2K0yqN5TXRt1H+UVkm4E5PIdKP8O OvnLTPQ8wVn1QShs0AtKRHEBDfdzitYVL/sGQkmelkt8xWALdG0fdSi8gvyPbtPEq8 8opQIcAbpWNqaLAdJX+U8vjwRek6kpbLHcwZ03aI= Subject: Re: [PATCH v8 2/5] IMA: Define an IMA hook to measure keys To: Eric Snowberg Cc: zohar@linux.ibm.com, linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org, keyrings@vger.kernel.org References: <20191118223818.3353-1-nramas@linux.microsoft.com> <20191118223818.3353-3-nramas@linux.microsoft.com> From: Lakshmi Ramasubramanian Message-ID: <98eeec95-cc19-2900-b96e-eadaac1b4a68@linux.microsoft.com> Date: Wed, 20 Nov 2019 15:40:14 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-integrity-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-integrity@vger.kernel.org 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; Until this change is in, please add the above line locally on entry to process_buffer_measurement() to get around the issue. thanks, -lakshmi