From: Baoquan He <bhe@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ye Xiaolong <xiaolong.ye@intel.com>,
Kees Cook <keescook@chromium.org>,
"Huang, Ying" <ying.huang@intel.com>, LKP ML <lkp@01.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [x86/KASLR] ed9f007ee6: -- System halted
Date: Fri, 1 Jul 2016 12:06:18 +0800 [thread overview]
Message-ID: <20160701040618.GA3372@x1.redhat.com> (raw)
In-Reply-To: <CAE9FiQUZSw-2XftWArfq3aBg6x7H-0Db_b-yNPbV71GeRxw7hw@mail.gmail.com>
On 06/30/16 at 05:24pm, Yinghai Lu wrote:
> On Wed, Jun 29, 2016 at 11:58 PM, Ye Xiaolong <xiaolong.ye@intel.com> wrote:
> > On Wed, Jun 29, 2016 at 09:49:12PM -0700, Yinghai Lu wrote:
> >>On Wed, Jun 29, 2016 at 1:29 PM, Huang, Ying <ying.huang@intel.com> wrote:
> >>> If you could provide a git branch for that, that will be easier for us
> >>> to test and more accurate for you to get the right patch to be tested.
> >>>
> >>
> >>Please check
> >>
> >>git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
> >>for-x86-v4.8-kaslr-debug
> >
> > Hi, yinghai
> >
> > Attached is the dmesg for the kernel which is built based on your
> > for-x86-v4.8-kaslr-debug branch.
>
> Thanks for capturing the boot log.
>
> early console in setup code
> early console in extract_kernel
> decompress_kernel:
> input: [0x0008fba276-0x000a8818ed]
> output: [0x0001000000-0x000a867c97] 0x09867c98: output_len
> [0x0001000000-0x0009768fff] 0x08769000: run_size
> [0x0001000000-0x000a867c97] 0x09867c98: output_run_size
> [0x0001000000-0x000a8affff] 0x098b0000: init_size
> ZO text/data: [0x000a8818ee-0x000a8affff]
> ZO heap: [0x000a888400-0x000a8983ff]
> VO bss/brk: [0x0009674000-0x0009768fff]
> booted via startup_32()
> Physical KASLR using RDTSC...
> Virtual KASLR using RDTSC...
> new output: [0x0006600000-0x000fe67c97] 0x09867c98: output_run_size
> virt_addr: 0x0024000000
> decompress: [0x0006600000-0x000fe67c97] <=== [0x0008fba276-0x000a8818ed]
>
> Decompressing Linux...
>
> XZ-compressed data is corrupt
>
> -- System halted
>
> Hi Kees/Baoquan,
>
> Looks like
>
> commit ed9f007ee68478f6a50ec9971ade25a0129a5c0e
> Author: Kees Cook <keescook@chromium.org>
> Date: Wed May 25 15:45:33 2016 -0700
>
> x86/KASLR: Extend kernel image physical address randomization to addresses l
> arger than 4G
I know why it happened, making patch. will reply soon.
>
>
> cause choose_random_location() return new output buffer
> new output: [0x0006600000-0x000fe67c97] 0x09867c98: output_run_size
>
> that is overlapped with input data.
> input: [0x0008fba276-0x000a8818ed]
> ....-0x000a8affff] 0x098b0000: init_size
>
> and input already is in mem_avoid.
next prev parent reply other threads:[~2016-07-01 4:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57712812.r6MdDSquaCRYkMnh%xiaolong.ye@intel.com>
2016-06-27 18:59 ` [x86/KASLR] ed9f007ee6: -- System halted Yinghai Lu
[not found] ` <20160628054354.GA9620@yexl-desktop>
[not found] ` <CAE9FiQV50UhjJDH89C_T7f2vxFDm7Hpjn78ZKtnfeygQcsf23w@mail.gmail.com>
2016-06-29 20:08 ` Yinghai Lu
2016-06-29 20:29 ` [LKP] " Huang, Ying
2016-06-30 4:49 ` Yinghai Lu
2016-06-30 6:58 ` Ye Xiaolong
2016-07-01 0:24 ` Yinghai Lu
2016-07-01 4:06 ` Baoquan He [this message]
2016-07-01 4:46 ` Baoquan He
2016-07-01 7:50 ` Baoquan He
2016-07-01 12:16 ` Ye Xiaolong
2016-07-01 13:14 ` Baoquan He
2016-07-01 13:25 ` Baoquan He
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=20160701040618.GA3372@x1.redhat.com \
--to=bhe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=xiaolong.ye@intel.com \
--cc=ying.huang@intel.com \
--cc=yinghai@kernel.org \
/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