From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752799AbcCASis (ORCPT ); Tue, 1 Mar 2016 13:38:48 -0500 Received: from mail.skyhub.de ([78.46.96.112]:43661 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751139AbcCASip (ORCPT ); Tue, 1 Mar 2016 13:38:45 -0500 Date: Tue, 1 Mar 2016 19:38:39 +0100 From: Borislav Petkov To: "Rountree, Barry L." Cc: "linux-kernel@vger.kernel.org" , George Spelvin , "a.p.zijlstra@chello.nl" , "acme@infradead.org" , "ak@linux.intel.com" , "andriy.shevchenko@linux.intel.com" , "brgerst@gmail.com" , "dan.j.williams@intel.com" , "dyoung@redhat.com" , "hpa@zytor.com" , "jolsa@redhat.com" , "Mcfadden, Marty Jay" , "luto@kernel.org" , "mingo@kernel.org" , "mingo@redhat.com" , "pavel@ucw.cz" , "viro@zeniv.linux.org.uk" , "x86@kernel.org" , "yu.c.chen@intel.com" , Thomas Gleixner , Travis Gummels , "Eastep, Jonathan M" , "len.brown@intel.com" , "prarit@redhat.com" Subject: Re: [PATCH 0/4] MSR: MSR: MSR Whitelist and Batch Introduction Message-ID: <20160301183839.GC22677@pd.tnic> References: <20160229145859.GA3724@pd.tnic> <20160229175318.14183.qmail@ns.horizon.com> <20160229182047.GD3724@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 01, 2016 at 06:29:59PM +0000, Rountree, Barry L. wrote: > ... And we can provide this access on production machines without > risking inadvertent or malicious scribbling on non-benign MSRs. And we > can do this with one simple, straightforward kernel module. So you can simply keep that module in your repo and apply it each time before doing a security review. It is not meant for upstream use anyway. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.