From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 6 Sep 2017 09:31:01 -0700 From: Tony Lindgren Message-ID: <20170906163100.GJ5024@atomide.com> References: <20170903120757.14968-1-ard.biesheuvel@linaro.org> <20170905164547.GA5024@atomide.com> <20170905193754.GD5024@atomide.com> <20170905212742.GG5024@atomide.com> <20170906162222.GI5024@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: [kernel-hardening] Re: [PATCH v2 00/29] implement KASLR for ARM To: Ard Biesheuvel Cc: "linux-arm-kernel@lists.infradead.org" , Kernel Hardening , Arnd Bergmann , Nicolas Pitre , Russell King , Kees Cook , Thomas Garnier , Marc Zyngier , Mark Rutland , Matt Fleming , Dave Martin List-ID: * Ard Biesheuvel [170906 09:26]: > On 6 September 2017 at 17:22, Tony Lindgren wrote: > > Sure was not able to reproduce it so far on BBB. But here's > > failed boot output from logicpd-torpedo-37xx-devkit. Will > > try some more booting on BBB too. ... > > 8< ------------------- > > Kernel image @ 0x81000000 [ 0x000000 - 0x426810 ] > > ## Flattened Device Tree blob at 84000000 > > Booting using the fdt blob at 0x84000000 > > Loading Device Tree to 86feb000, end 86fff2d5 ... OK > > > > Starting kernel ... > > > > regions.image_size:00e00000 > > regions.pa_start:80000000 > > regions.pa_end:88000000 > > regions.zimage_start:81000000 > > regions.zimage_size:00437830 > > regions.dtb_start:86feb000 > > regions.dtb_size:00012000 > > regions.initrd_start:00000000 > > regions.initrd_size:00000000 > > num:0000002f > > num:00000029 > > *kaslr_offset:07400000 > > Uncompressing Linux... > > Is that all? Does it hang while decompressing the kernel? Yeah so it seems. If we had uncompress overwriting something because of the increase in size it should happen on every boot though, not once every five boots or so. Regards, TOny From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Wed, 6 Sep 2017 09:31:01 -0700 Subject: [PATCH v2 00/29] implement KASLR for ARM In-Reply-To: References: <20170903120757.14968-1-ard.biesheuvel@linaro.org> <20170905164547.GA5024@atomide.com> <20170905193754.GD5024@atomide.com> <20170905212742.GG5024@atomide.com> <20170906162222.GI5024@atomide.com> Message-ID: <20170906163100.GJ5024@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Ard Biesheuvel [170906 09:26]: > On 6 September 2017 at 17:22, Tony Lindgren wrote: > > Sure was not able to reproduce it so far on BBB. But here's > > failed boot output from logicpd-torpedo-37xx-devkit. Will > > try some more booting on BBB too. ... > > 8< ------------------- > > Kernel image @ 0x81000000 [ 0x000000 - 0x426810 ] > > ## Flattened Device Tree blob at 84000000 > > Booting using the fdt blob at 0x84000000 > > Loading Device Tree to 86feb000, end 86fff2d5 ... OK > > > > Starting kernel ... > > > > regions.image_size:00e00000 > > regions.pa_start:80000000 > > regions.pa_end:88000000 > > regions.zimage_start:81000000 > > regions.zimage_size:00437830 > > regions.dtb_start:86feb000 > > regions.dtb_size:00012000 > > regions.initrd_start:00000000 > > regions.initrd_size:00000000 > > num:0000002f > > num:00000029 > > *kaslr_offset:07400000 > > Uncompressing Linux... > > Is that all? Does it hang while decompressing the kernel? Yeah so it seems. If we had uncompress overwriting something because of the increase in size it should happen on every boot though, not once every five boots or so. Regards, TOny