From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756561AbcDDXF1 (ORCPT ); Mon, 4 Apr 2016 19:05:27 -0400 Received: from e23smtp05.au.ibm.com ([202.81.31.147]:60051 "EHLO e23smtp05.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751605AbcDDXFZ (ORCPT ); Mon, 4 Apr 2016 19:05:25 -0400 X-IBM-Helo: d23dlp01.au.ibm.com X-IBM-MailFrom: zohar@linux.vnet.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org;linux-security-module@vger.kernel.org Message-ID: <1459811036.6228.30.camel@linux.vnet.ibm.com> Subject: Re: [PATCH v2 5/5] LSM: LoadPin for kernel file loading restrictions From: Mimi Zohar To: Kees Cook Cc: James Morris , "Serge E. Hallyn" , Andrew Morton , Kalle Valo , Mauro Carvalho Chehab , Joe Perches , Guenter Roeck , Jiri Slaby , Paul Moore , Stephen Smalley , Casey Schaufler , Andreas Gruenbacher , Andy Shevchenko , Rasmus Villemoes , Ulf Hansson , Vitaly Kuznetsov , linux-security-module , LKML Date: Mon, 04 Apr 2016 19:03:56 -0400 In-Reply-To: References: <1459199662-16558-1-git-send-email-keescook@chromium.org> <1459199662-16558-6-git-send-email-keescook@chromium.org> <1459459442.2657.51.camel@linux.vnet.ibm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 (3.12.11-1.fc21) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16040423-0017-0000-0000-00000416876D Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2016-04-04 at 12:31 -0700, Kees Cook wrote: > On Thu, Mar 31, 2016 at 2:24 PM, Mimi Zohar wrote: > > On Mon, 2016-03-28 at 14:14 -0700, Kees Cook wrote: > > > >> +static const char *id_str[READING_MAX_ID] = { > >> + [READING_FIRMWARE] = "firmware", > >> + [READING_MODULE] = "kernel module", > >> + [READING_KEXEC_IMAGE] = "kexec image", > >> + [READING_KEXEC_INITRAMFS] = "kexec initramfs", > >> + [READING_POLICY] = "security policy", > >> +}; > >> + > I wonder if there should be a function that returns a const string for > each kernel_read_file_id enum so users of the enum don't need to do > it? Right, having a single, corresponding, string array would be good. Some of the strings in id_str[] have blanks, which might be problematic for the audit subsystem, and would need to be replaced with a hyphen or underscore. Mimi