From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Frans Pop <elendil@planet.nl>, Ian Campbell <ijc@hellion.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [regression?] 2.6.26 floppy boot failure with kernel packed using 'upx'
Date: Thu, 10 Jul 2008 13:49:25 -0400 [thread overview]
Message-ID: <48764BA5.7050104@zytor.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0807101015010.11076@woody.linux-foundation.org>
Linus Torvalds wrote:
>
> On Thu, 10 Jul 2008, Frans Pop wrote:
>> Important factor here is that we "pack" the kernel using upx [1] (in order
>> to fit everything on a floppy). The original (unpacked) kernel after this
>> commit boots fine, only a packed version fails.
>> We have tried upx versions 2.01, 3.01 and 3.03, all with same result.
>
> Ok, I do not consider this to be a regression.
>
> Clearly UPX is expecting a very specific kernel format, and clearly UPX
> just needs to be updated for the changes.
>
> That said, if some UPX person can explain what it is that UPX needs, maybe
> we can add some format markers into the kernel (and perhaps some extra
> header info) so that future format changes are transparent or at least
> break in obvious ways.
>
The issue with UPX is that UPX actually wants to replace the kernel
decompressor, which also does other tasks (relocation and ELF parsing)
in recent kernels.
-hpa
next prev parent reply other threads:[~2008-07-10 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 4:54 [regression?] 2.6.26 floppy boot failure with kernel packed using 'upx' Frans Pop
2008-07-10 7:47 ` Ian Campbell
2008-07-10 9:25 ` Frans Pop
2008-07-10 13:49 ` H. Peter Anvin
2008-07-10 17:17 ` Linus Torvalds
2008-07-10 17:49 ` H. Peter Anvin [this message]
2008-07-10 18:18 ` Frans Pop
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=48764BA5.7050104@zytor.com \
--to=hpa@zytor.com \
--cc=elendil@planet.nl \
--cc=ijc@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.