linux-kernel - Re: [regression?] 2.6.26 floppy boot failure with kernel packed using 'upx'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Jul 2008 10:17:17 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Frans Pop <elendil@...net.nl>
cc:	Ian Campbell <ijc@...lion.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, Peter Anvin <hpa@...or.com>
Subject: Re: [regression?] 2.6.26 floppy boot failure with kernel packed
 using 'upx'



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.

			Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/