From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EFD82C32751 for ; Wed, 31 Jul 2019 20:49:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AC2BC2171F for ; Wed, 31 Jul 2019 20:49:43 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=hansenpartnership.com header.i=@hansenpartnership.com header.b="TqkztYgF"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=hansenpartnership.com header.i=@hansenpartnership.com header.b="mm1ytu3h" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728136AbfGaUtn (ORCPT ); Wed, 31 Jul 2019 16:49:43 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:34950 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726553AbfGaUtn (ORCPT ); Wed, 31 Jul 2019 16:49:43 -0400 Received: from localhost (localhost [127.0.0.1]) by bedivere.hansenpartnership.com (Postfix) with ESMTP id 5ADFB8EE12F; Wed, 31 Jul 2019 13:49:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hansenpartnership.com; s=20151216; t=1564606182; bh=aonueY2GL5wo/ScyliCdbuSAXa73QdYEqPgbmasyuTA=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=TqkztYgFvFk8m5p1D8o41OUYDQxx3oH88tnest8OOEFTrplJzxkrEIl3RTe9sVDTd 0/JDBZGGDOJiJmBGU6nC2vUqZ969JgBVwqxB3olO+lJc3X8WhOwIXWJLQELmt4cUIv Q9yLzk62uCRZZ6SruC1Ph1Dwa+/aPnLqtNhMuevU= Received: from bedivere.hansenpartnership.com ([127.0.0.1]) by localhost (bedivere.hansenpartnership.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MjMpDV_FTtoX; Wed, 31 Jul 2019 13:49:42 -0700 (PDT) Received: from jarvis.lan (unknown [50.35.71.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bedivere.hansenpartnership.com (Postfix) with ESMTPSA id C83648EE10C; Wed, 31 Jul 2019 13:49:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hansenpartnership.com; s=20151216; t=1564606181; bh=aonueY2GL5wo/ScyliCdbuSAXa73QdYEqPgbmasyuTA=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=mm1ytu3hUoxpFW6AuZNf8ebBBEu4HjHuGTEGTL7SZNnn3oRQenv2Nbt3cbpdPMUAg Wo4NnX/5AtUdHJ+K1m7hSthqmxW4fd5QU72OojK4otM5vuxNLt66iX7SXwoPuT+YU7 flRcqc9S76t6uLyP7oeNJNJl05OupU2odxK8cWs8= Message-ID: <1564606179.3319.70.camel@HansenPartnership.com> Subject: Re: Compressed kernels currently won't boot From: James Bottomley To: Helge Deller , Sven Schnelle Cc: Parisc List Date: Wed, 31 Jul 2019 13:49:39 -0700 In-Reply-To: <2fc63e1d-dbcf-924b-e134-e5c2dcc75260@gmx.de> References: <1564591443.3319.30.camel@HansenPartnership.com> <20190731173016.GA23520@t470p.stackframe.org> <1564595402.3319.40.camel@HansenPartnership.com> <1564602012.3319.45.camel@HansenPartnership.com> <20190731194413.GB23520@t470p.stackframe.org> <0084df92-ca9f-7600-187d-bc6123f30fd1@gmx.de> <1564602968.3319.56.camel@HansenPartnership.com> <2fc63e1d-dbcf-924b-e134-e5c2dcc75260@gmx.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-parisc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-parisc@vger.kernel.org On Wed, 2019-07-31 at 22:19 +0200, Helge Deller wrote: > On 31.07.19 21:56, James Bottomley wrote: > > On Wed, 2019-07-31 at 21:46 +0200, Helge Deller wrote: > > > On 31.07.19 21:44, Sven Schnelle wrote: > > > > Hi James, > > > > > > > > On Wed, Jul 31, 2019 at 12:40:12PM -0700, James Bottomley > > > > wrote: > > > > > > > > > What about causing the compressed make to build both a > > > > > stripped and a non-stripped bzImage (say sbzImage and > > > > > bzImage). That way you always have the stripped one > > > > > available for small size things like boot from tape or > > > > > DVD? but in the usual case we use the bzImage with full > > > > > contents. > > > > > > > > In that case we would also need to build two lifimages - how > > > > about adding a config option option? Something like "Strip > > > > debug information from compressed kernel images"? > > > > > > I agree, two lifimages don't make sense. Only one vmlinuz gets > > > installed. Instead of the config option, I tink my latest patch > > > is better. > > > > It doesn't solve the problem that if a stripped compressed image is > > > > > 128kb then it overwrites the decompress area starting at 0x00100000 > > so we can't decompress the end because we've already overwritten it > > before the decompressor gets to it. > > I don't get this point. > hppa64-linux-gnu-objdump -h vmlinuz > shows: > Sections: > Idx Name Size VMA LMA File > off Algn > 0 > .head.text 00000084 00000000000e0000 00000000000e0000 00001000 > 2**2 > CONTENTS, ALLOC, LOAD, READONLY, CODE > 1 > .opd 00000340 00000000000e0090 00000000000e0090 00001090 > 2**3 > CONTENTS, ALLOC, LOAD, DATA > 2 > .dlt 00000160 00000000000e03d0 00000000000e03d0 000013d0 > 2**3 > CONTENTS, ALLOC, LOAD, DATA > 3 .rodata.compressed > 01f3c2b0 00000000000e0530 00000000000e0530 00001530 2**0 > CONTENTS, ALLOC, LOAD, DATA > 4 > .text 00005cc0 000000000201d000 000000000201d000 01f3e000 > 2**7 > CONTENTS, ALLOC, LOAD, READONLY, CODE > 5 > .data 00000060 0000000002022cc0 0000000002022cc0 01f43cc0 > 2**3 > CONTENTS, ALLOC, LOAD, DATA > > Only .head.text gets loaded at e0000, and it is basically just a few > bytes which sets-up registers and jump to .text segment (at 0201d000 > in this case). Actually, you're looking at the wrong thing, you want to look at the program header (the segments) not the section header. It's the program header we load. If I extract this from the current debian kernel we get jejb@ion:~/git/linux-build/arch/parisc/boot/compressed> readelf -l /boot/vmlinuz-4.19.0-5-parisc64-smp Elf file type is EXEC (Executable file) Entry point 0xe0000 There are 4 program headers, starting at offset 64 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flags Align PHDR 0x0000000000000040 0x0000000000001040 0x0000000000000000 0x00000000000000e0 0x00000000000000e0 R E 0x8 LOAD 0x0000000000001000 0x00000000000e0000 0x00000000000e0000 0x00000000000004d8 0x00000000000004d8 RWE 0x1000 LOAD 0x0000000000002000 0x0000000001400000 0x0000000001400000 0x00000000003dd46c 0x00000000003e1000 RWE 0x1000 GNU_STACK 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 RWE 0x10 Section to Segment mapping: Segment Sections... 00 01 .head.text .opd .dlt 02 .text .data .rodata .eh_frame .bss 03 The two LOAD sections corresponding to what PALO actually loads. The problem happens if the length of the first load section is bigger than 0x20000. Now if you look what happens after your change: jejb@ion:~/git/linux-build/build/parisc64/arch/parisc/boot> readelf -l bzImage Elf file type is EXEC (Executable file) Entry point 0xe0000 There are 4 program headers, starting at offset 64 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flags Align PHDR 0x0000000000000040 0x0000000000001040 0x0000000000000000 0x00000000000000e0 0x00000000000000e0 R E 0x8 LOAD 0x0000000000001000 0x00000000000e0000 0x00000000000e0000 0x00000000004ae760 0x00000000004ae760 RWE 0x1000 LOAD 0x00000000004b0000 0x000000000118a000 0x000000000118a000 0x0000000000006044 0x000000000000a000 RWE 0x1000 GNU_STACK 0 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000 RWE 0x10 Section to Segment mapping: Segment Sections... 00 01 .head.text .opd .dlt .rodata.compressed 02 .text .data .rodata .eh_frame .bss 03 So the first section tries to load between 0x000e0000-0x0058e760 and that's overwritten at 0x00100000 when the decompression starts because 0x00100000 is our KERNEL_BINARY_TEXT_START. The result for me is that I get the Decompressing linux ... message followed by a HPMC. James