Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support

From	Ingo Molnar <mingo@kernel.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support
Date	2016-04-15 09:00 +0200
Message-ID	<ro5Ts-79F-11@gated-at.bofh.it> (permalink)
References	(5 earlier) <rnIDx-5In-21@gated-at.bofh.it> <rnR49-3Fm-101@gated-at.bofh.it> <rnTIE-5Nb-29@gated-at.bofh.it> <ro3eV-5du-1@gated-at.bofh.it> <ro41k-5J1-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

* Kees Cook <keescook@chromium.org> wrote:

> On Thu, Apr 14, 2016 at 9:08 PM, Baoquan He <bhe@redhat.com> wrote:

> >> I will split these chunks up into the correct patches and resend the series. 
> >> If you get a chance, can you double-check this?
> >
> > Yes, these changes sounds great. I checked the series you posted, and have to 
> > say you make them look much better. The change logs are perfect and great code 
> > refactoring. Just one little bit thing, here:
> >
> > [kees: rewrote changelog, refactored goto into while, limit 32-bit to 1G] in 
> > patch [PATCH v5 19/21] x86, KASLR: Add physical address randomization >4G
> >
> > In i386 KERNEL_IMAGE_SIZE is kept to be 0x20000000, namely 512M, w/o kaslr 
> > enabled. So here I guess it's a typo, should be "limit 32-bit to 1G". And what 
> > I said is wrong about upper limit yesterday, in fact i386 can put kernel in 
> > [16M, 896M), not 768M. But KERNEL_IMAGE_SIZE is good enough for i386 for now.
> 
> Ah yeah, thanks. If we do a v6, I'll update the typo. I was going to say "limit 
> 32-bit to KERNEL_IMAGE_SIZE" but it was going to line-wrap.
> :P

No need to resend, I've fixed the changelog.

Thanks,

	Ingo

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support Baoquan He <bhe@redhat.com> - 2016-04-05 04:00 +0200
  Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support Kees Cook <keescook@chromium.org> - 2016-04-05 22:10 +0200
    Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support Ingo Molnar <mingo@kernel.org> - 2016-04-13 12:30 +0200
      Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support Kees Cook <keescook@chromium.org> - 2016-04-13 16:20 +0200
        Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support Kees Cook <keescook@chromium.org> - 2016-04-14 08:10 +0200
          Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support Baoquan He <bhe@redhat.com> - 2016-04-14 08:30 +0200
          Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support Baoquan He <bhe@redhat.com> - 2016-04-14 17:10 +0200
            Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support Kees Cook <keescook@chromium.org> - 2016-04-14 20:00 +0200
              Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support Baoquan He <bhe@redhat.com> - 2016-04-15 06:10 +0200
                Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support Kees Cook <keescook@chromium.org> - 2016-04-15 07:00 +0200
                Re: [PATCH v4 00/20] x86, boot: kaslr cleanup and 64bit kaslr support Ingo Molnar <mingo@kernel.org> - 2016-04-15 09:00 +0200

csiph-web