lkml.org 
[lkml]   [2017]   [Dec]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch V181 49/54] x86/dumpstack: Indicate in Oops whether pti is configured and enabled
On Wed, 20 Dec 2017, Thomas Gleixner wrote:

> From: Vlastimil Babka <vbabka@suse.cz>
>
> CONFIG_PAGE_TABLE_ISOLATION is relatively new and intrusive feature that may
> still have some corner cases which could take some time to manifest and be
> fixed. It would be useful to have Oops messages indicate whether it was
> enabled for building the kernel, and whether it was disabled during boot.
>
> Example of fully enabled:
>
> Oops: 0001 [#1] SMP PTI
>
> Example of enabled during build, but disabled during boot:
>
> Oops: 0001 [#1] SMP NOPTI
>
> We can decide to remove this after the feature has been tested in the field
> long enough.
>
> [ tglx: Made it use boot_cpu_has() as requested by Borislav ]
>
> Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Reviewed-by: Eduardo Valentin <eduval@amazon.com>
> Acked-by: Dave Hansen <dave.hansen@intel.com>

FWIW

Acked-by: Jiri Kosina <jkosina@suse.cz>

I've had a much more stupid variant of this when fuzzing pti/nopti kernels
(distro backports, of course), and it was really helpful when diving into
the crashes.

Thanks,

--
Jiri Kosina
SUSE Labs

\
 
 \ /
  Last update: 2017-12-20 23:04    [W:0.312 / U:2.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site