Re: [tip:x86/kaslr] x86, relocs: Add more per-cpu gold special cases

[H. Peter Anvin]

My guess is that the 95 addresses are randomized and the 82 address is an address which failed to relocate.

Ingo Molnar <mingo@xxxxxxxxxx> wrote:
>
>* tip-bot for Michael Davidson <tipbot@xxxxxxxxx> wrote:
>
>> Commit-ID:  d751c169e9a6f0f853346f1184881422bd10b3c2
>> Gitweb:    
>http://git.kernel.org/tip/d751c169e9a6f0f853346f1184881422bd10b3c2
>> Author:     Michael Davidson <md@xxxxxxxxxx>
>> AuthorDate: Thu, 10 Oct 2013 18:39:54 -0700
>> Committer:  H. Peter Anvin <hpa@xxxxxxxxxxxxxxx>
>> CommitDate: Sun, 13 Oct 2013 03:11:57 -0700
>> 
>> x86, relocs: Add more per-cpu gold special cases
>
>I'm quite sure that one of the recent x86/kaslr changes causes this
>early 
>x86-64 crash:
>
> BRK [0x179fb000, 0x179fbfff] PGTABLE
> BRK [0x179fc000, 0x179fcfff] PGTABLE
> BRK [0x179fd000, 0x179fdfff] PGTABLE
>PANIC: early exception 0e rip 10:ffffffff95203b9c error 0 cr2
>ffffffff82a04a58
> CPU: 0 PID: 0 Comm: swapper Not tainted 3.12.0-rc5+ #229838
>Hardware name: System manufacturer System Product Name/A8N-E, BIOS ASUS
>
> A8N-E ACPI BIOS Revision 1008 08/22/2005
>PANIC: early exception 0e rip 10:ffffffff95203e01 error 0 cr2
>ffffffff82a04a58
>
>Config and crashlog attached.
>
>ffffffff95203b9c and ffffffff95203e01 is well outside the executable
>range 
>is thus not in the vmlinux.
>
>ffffffff82a04a58 is:
>
>ffffffff82a03000 t init_per_cpu__gdt_page
>ffffffff82bcd000 t _sinittext
>
>Thanks,
>
>	Ingo

-- 
Sent from my mobile phone.  Please pardon brevity and lack of formatting.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/