Re: [PATCH] x86: do not leak kernel page mapping locations

2013-02-07 Thread H. Peter Anvin
On 02/07/2013 09:44 AM, Kees Cook wrote: > Without this patch, it is trivial to determine kernel page mappings by > examining the error code reported to dmesg[1]. Instead, declare the entire > kernel memory space as a violation of a present page. > > Additionally, since show_unhandled_signals is

[PATCH] x86: do not leak kernel page mapping locations

2013-02-07 Thread Kees Cook
Without this patch, it is trivial to determine kernel page mappings by examining the error code reported to dmesg[1]. Instead, declare the entire kernel memory space as a violation of a present page. Additionally, since show_unhandled_signals is enabled by default, switch branch hinting to the

Re: [PATCH] x86: do not leak kernel page mapping locations

2013-02-07 Thread H. Peter Anvin
On 02/07/2013 09:44 AM, Kees Cook wrote: Without this patch, it is trivial to determine kernel page mappings by examining the error code reported to dmesg[1]. Instead, declare the entire kernel memory space as a violation of a present page. Additionally, since show_unhandled_signals is

[PATCH] x86: do not leak kernel page mapping locations

2013-02-07 Thread Kees Cook
Without this patch, it is trivial to determine kernel page mappings by examining the error code reported to dmesg[1]. Instead, declare the entire kernel memory space as a violation of a present page. Additionally, since show_unhandled_signals is enabled by default, switch branch hinting to the