From: Baoquan He <bhe@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Kees Cook <keescook@chromium.org>,
Vivek Goyal <vgoyal@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 7/9] get the random phy addr according to slot_area info
Date: Tue, 3 Mar 2015 19:42:31 +0800 [thread overview]
Message-ID: <20150303114231.GC8466@dhcp-16-105.nay.redhat.com> (raw)
In-Reply-To: <CAE9FiQWmY=DLespBxJVhORdBs+FH4y6BDqbdSRLZ9EEYKm6v3Q@mail.gmail.com>
On 03/03/15 at 12:45am, Yinghai Lu wrote:
> On Mon, Mar 2, 2015 at 6:58 AM, Baoquan He <bhe@redhat.com> wrote:
> > Now random value can be used to get related slot info stored in
> > slot_area, mainly use slot_area.num to position which slot is target.
> > With this slot its starting address is returned as the physical
> > address where kernel will put.
> >
> > @@ -362,7 +364,7 @@ repeat:
> > goto repeat;
> > }
> >
> > -static unsigned long find_random_addr(unsigned long minimum,
> > +static unsigned long find_random_phy_addr(unsigned long minimum,
> > unsigned long size)
>
Hi Yinghai,
Thanks for testing and reviewing.
Yes, I forgot to change calling name. Must be dizzy during making patch.
Will change.
> You forgot to change calling name.
>
> got:
>
> arch/x86/boot/compressed/aslr.o: In function `choose_kernel_location':
> aslr.c:(.text+0x163): undefined reference to `find_random_addr'
> make[2]: *** [arch/x86/boot/compressed/vmlinux] Error 1
> make[1]: *** [arch/x86/boot/compressed/vmlinux] Error 2
>
> Please make the patch set bisect-able.
Ok, will rearrange patches.
>
> after fixing that, on the system with 4G ram: i got:
>
> early console in decompress_kernel
> KASLR using RDTSC...
> decompress_kernel:
> input: [0x13f5ed3b4-0x13ff6a64b], output: 0x153000000, heap:
Here input means the region where kernel was linked to load?
In normal kernel the linked address is 0x1000000. In your input region
the result of ALIGN(0x13f5ed3b4, CONFIG_PHYSICAL_ALIGN) is 0x140000000.
And size of this region is smaller than 16M. It should return in
process_e820_entry() with two checks.
I guess you use kexec or a special bootloader to put kernel in this
load address.
I will check code again it doesn't handle this case correctly.
> [0x13ff76000-0x13ff7dfff]
>
> Decompressing Linux... xz...
>
> XZ-compressed data is corrupt
>
>
> without the patch, I have:
>
> early console in decompress_kernel
> KASLR could not find suitable E820 region...
> decompress_kernel:
> input: [0x13f5ee3b4-0x13ff6b64b], output: 0x13cc00000, heap:
> [0x13ff76000-0x13ff7dfff]
>
> Decompressing Linux... xz... Parsing ELF... done.
> ...
> [ 0.016848] e820: BIOS-provided physical RAM map (sanitized by setup):
> [ 0.018854] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
> [ 0.020982] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
> [ 0.023166] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
> [ 0.025783] BIOS-e820: [mem 0x0000000000100000-0x00000000bffdffff] usable
> [ 0.027901] BIOS-e820: [mem 0x00000000bffe0000-0x00000000bfffffff] reserved
> [ 0.030079] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
> [ 0.032252] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
> [ 0.034437] BIOS-e820: [mem 0x0000000100000000-0x000000013fffffff] usable
>
> so you code now select range that is out of boundary to non ram area.
>
> Thanks
>
> Yinghai
next prev parent reply other threads:[~2015-03-03 11:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 14:58 [PATCH v2 0/9] randomize kernel physical address and virtual address separately Baoquan He
2015-03-02 14:58 ` [PATCH v2 1/9] remove a unused function parameter Baoquan He
2015-03-03 18:32 ` Yinghai Lu
2015-03-04 15:48 ` Baoquan He
2015-03-02 14:58 ` [PATCH v2 2/9] a bug that relocation can not be handled when kernel is loaded above 2G Baoquan He
2015-03-02 14:58 ` [PATCH v2 3/9] make kernel be able to load above 4G in boot stage Baoquan He
2015-03-02 15:58 ` Baoquan He
2015-03-02 14:58 ` [PATCH v2 4/9] introduce struct slot_area to manage randomization slot info Baoquan He
2015-03-02 14:58 ` [PATCH v2 5/9] add mem_min_overlap to find the first avoid region within a memory region Baoquan He
2015-03-02 14:58 ` [PATCH v2 6/9] change process_e820_entry to store slot info into slot_area Baoquan He
2015-03-02 14:58 ` [PATCH v2 7/9] get the random phy addr according to slot_area info Baoquan He
2015-03-03 8:45 ` Yinghai Lu
2015-03-03 11:42 ` Baoquan He [this message]
2015-03-03 16:14 ` Yinghai Lu
2015-03-04 12:08 ` Baoquan He
2015-03-04 15:39 ` Baoquan He
2015-03-04 21:35 ` Yinghai Lu
2015-03-05 0:12 ` Yinghai Lu
2015-03-05 1:55 ` Baoquan He
2015-03-05 0:30 ` Yinghai Lu
2015-03-05 1:48 ` Baoquan He
2015-03-04 21:28 ` Kees Cook
2015-03-04 23:43 ` Baoquan He
2015-03-02 14:58 ` [PATCH v2 8/9] introduce fetch_random_virt_offset to randomize the kernel text mapping address Baoquan He
2015-03-02 14:58 ` [PATCH v2 9/9] change the relocations behavior for kaslr on x86_64 Baoquan He
2015-03-04 23:16 ` Yinghai Lu
2015-03-04 23:41 ` Baoquan He
2015-03-05 15:57 ` [PATCH v2 0/9] randomize kernel physical address and virtual address separately Baoquan He
2015-03-06 1:37 ` Yinghai Lu
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=20150303114231.GC8466@dhcp-16-105.nay.redhat.com \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.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
all inboxes | Powered by JetHome®