From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: [PATCH V33 21/30] x86/mmiotrace: Lock down the testmmiotrace module Date: Wed, 26 Jun 2019 08:46:18 -0400 Message-ID: <20190626084618.49c6a311@gandalf.local.home> References: <20190621011941.186255-1-matthewgarrett@google.com> <20190621011941.186255-22-matthewgarrett@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20190621011941.186255-22-matthewgarrett@google.com> Sender: linux-kernel-owner@vger.kernel.org To: Matthew Garrett Cc: jmorris@namei.org, linux-security@vger.kernel.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, David Howells , Thomas Gleixner , Matthew Garrett , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org List-Id: linux-api@vger.kernel.org On Thu, 20 Jun 2019 18:19:32 -0700 Matthew Garrett wrote: > From: David Howells > > The testmmiotrace module shouldn't be permitted when the kernel is locked > down as it can be used to arbitrarily read and write MMIO space. This is > a runtime check rather than buildtime in order to allow configurations > where the same kernel may be run in both locked down or permissive modes > depending on local policy. > > Suggested-by: Thomas Gleixner > Signed-off-by: David Howells Signed-off-by: Matthew Garrett > cc: Thomas Gleixner Acked-by: Steven Rostedt (VMware) -- Steve > cc: Ingo Molnar > cc: "H. Peter Anvin" > cc: x86@kernel.org > ---