mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [regression?] 2.6.26 floppy boot failure with kernel packed using 'upx'
Date: Thu, 10 Jul 2008 11:25:32 +0200	[thread overview]
Message-ID: <200807101125.34275.elendil@planet.nl> (raw)
In-Reply-To: <1215676061.3452.29.camel@cthulhu.hellion.org.uk>

On Thursday 10 July 2008, Ian Campbell wrote:
> On Thu, 2008-07-10 at 06:54 +0200, Frans Pop wrote:
> > The issue can also be reproduced using qemu without booting the
> > floppy itself. For the "bad" image:
> > # Boots correctly (but fails when mounting root fs):
> > $ qemu -kernel vmlinuz -hda /dev/zero
> > # Fails:
> > $ qemu -kernel vmlinuz.upx -hda /dev/zero
>
> I can repro this.
>
> All in all I'd say it should be treated as a new subtype/variant which
> UPX should support. I'd say adding support for bzImage v2.08 to UPX
> would be pretty easy for someone who knows the code base (I couldn't
> even find the decompressor code, but then it's pre-coffee time here..).

Thanks for the quick and complete reply Ian. I already expected this but 
thought it would at least be useful to inform people here of the issue 
(and get it indexed for search engines).

I have no problems with it not being treated as a bug/regression.

I've now filed a bug report against upx:
http://sourceforge.net/tracker/?func=detail&aid=2014835&group_id=2331&atid=102331

Cheers,
FJP

  reply	other threads:[~2008-07-10  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10  4:54 Frans Pop
2008-07-10  7:47 ` Ian Campbell
2008-07-10  9:25   ` Frans Pop [this message]
2008-07-10 13:49 ` H. Peter Anvin
2008-07-10 17:17 ` Linus Torvalds
2008-07-10 17:49   ` H. Peter Anvin
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=200807101125.34275.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=hpa@zytor.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome