[PATCH V31 19/25] x86/mmiotrace: Lock down the testmmiotrace module

Matthew Garrett mjg59 at google.com
Wed Mar 27 16:55:20 UTC 2019

On Wed, Mar 27, 2019 at 8:57 AM Steven Rostedt <rostedt at goodmis.org> wrote:
> On Tue, 26 Mar 2019 11:27:35 -0700
> Matthew Garrett <matthewgarrett at google.com> wrote:
> > From: David Howells <dhowells at redhat.com>
> >
> > 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.
> >
> Acked-by: Steven Rostedt (VMware) <rostedt at goodmis.org>
> I'm curious. Should there be a mode to lockdown the tracefs directory
> too? As that can expose addresses.

That sounds like a reasonable thing to do in the confidentiality mode,
I don't think it'd be necessary in the integrity mode.

More information about the Linux-security-module-archive mailing list