[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160203104823.GA21257@gmail.com>
Date: Wed, 3 Feb 2016 11:48:23 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: "Luck, Tony" <tony.luck@...el.com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andy Lutomirski <luto@...capital.net>,
Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Brian Gerst <brgerst@...il.com>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] Dump interesting arch/platform info
* Borislav Petkov <bp@...en8.de> wrote:
> On Mon, Feb 01, 2016 at 11:29:03PM +0000, Luck, Tony wrote:
> > On a high core count, multi-socket, machine I see almost 10K lines
> > of output from this. If you add other things it will become a bit
> > of a jumble to parse.
>
> Always thinking big... :-)
>
> > Perhaps the module name "archinfo" is fine, but each separate thing
> > it shows should get its own file. Starting with:
> >
> > /sys/kernel/debug/x86/gdtinfo
> >
> > for the current output?
>
> Right, or put everything under a directory "archinfo":
>
> /sys/kernel/debug/x86/archinfo/ ... gdt
> ... msrs
>
> ...
>
> and so on.
>
> Yap, sounds better. Thanks!
Agreed. We used to have something like this but then removed it due to various
problems - but the concept itself is fine.
Note that these can be pretty security sensitive pieces of information, and can
also expose ASLR/KASLR details, so the VFS interface needs to be a strictly
root-only thing.
Thanks,
Ingo
Powered by blists - more mailing lists