From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751310AbcDFQYy (ORCPT ); Wed, 6 Apr 2016 12:24:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34686 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750748AbcDFQYx (ORCPT ); Wed, 6 Apr 2016 12:24:53 -0400 Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <1459911605.3166.13.camel@linux.vnet.ibm.com> References: <1459911605.3166.13.camel@linux.vnet.ibm.com> To: Mimi Zohar Cc: dhowells@redhat.com, linux-security-module@vger.kernel.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] IMA: Use the system trusted keyrings instead of .ima_mok (update) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4391.1459959890.1@warthog.procyon.org.uk> Date: Wed, 06 Apr 2016 17:24:50 +0100 Message-ID: <4392.1459959890@warthog.procyon.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Looking in digsig.c, I see: #ifdef CONFIG_INTEGRITY_TRUSTED_KEYRING static bool init_keyring __initdata = true; #else static bool init_keyring __initdata; #endif Since this doesn't ever appear to be altered, should integrity_init_keyring() just be made conditionally compiled? David