From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, keescook@chromium.org,
md@google.com, tglx@linutronix.de, hpa@linux.intel.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/kaslr] x86, relocs: Add more per-cpu gold special cases
Date: Mon, 14 Oct 2013 07:19:22 -0700 [thread overview]
Message-ID: <007cdb12-9fc7-4744-8686-695891b926a3@email.android.com> (raw)
In-Reply-To: <20131014083035.GA20976@gmail.com>
My guess is that the 95 addresses are randomized and the 82 address is an address which failed to relocate.
Ingo Molnar <mingo@kernel.org> wrote:
>
>* tip-bot for Michael Davidson <tipbot@zytor.com> wrote:
>
>> Commit-ID: d751c169e9a6f0f853346f1184881422bd10b3c2
>> Gitweb:
>http://git.kernel.org/tip/d751c169e9a6f0f853346f1184881422bd10b3c2
>> Author: Michael Davidson <md@google.com>
>> AuthorDate: Thu, 10 Oct 2013 18:39:54 -0700
>> Committer: H. Peter Anvin <hpa@linux.intel.com>
>> 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.
next prev parent reply other threads:[~2013-10-14 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 1:39 [PATCH v2] x86, relocs: add " Kees Cook
2013-10-13 12:01 ` [tip:x86/kaslr] x86, relocs: Add " tip-bot for Michael Davidson
2013-10-14 8:30 ` Ingo Molnar
2013-10-14 9:38 ` Ingo Molnar
2013-10-14 14:19 ` H. Peter Anvin [this message]
2013-10-14 16:28 ` H. Peter Anvin
2013-10-14 20:47 ` Kees Cook
2013-10-15 6:04 ` Ingo Molnar
2013-10-15 15:42 ` Kees Cook
2013-10-15 16:03 ` Ingo Molnar
2013-10-15 17:22 ` Kees Cook
2013-10-16 6:56 ` Ingo Molnar
2013-10-16 14:53 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=007cdb12-9fc7-4744-8686-695891b926a3@email.android.com \
--to=hpa@zytor.com \
--cc=hpa@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=md@google.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®