linux-kernel - Re: PATCH/RFC: bzImage payload as compressed ELF file.

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:	Tue, 29 Jan 2008 09:31:18 +0000
From:	Ian Campbell <ijc@...lion.org.uk>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org, Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: PATCH/RFC: bzImage payload as compressed ELF file.


On Mon, 2008-01-28 at 15:20 -0800, H. Peter Anvin wrote:
> Ian Campbell wrote:
> > 
> > What would be the preferred way of allowing bootloaders/domain builders
> > to find the compressed payload? Tacking the offset from the end onto the
> > end as I have done for the moment seems pretty skanky...
> > 
> 
> As Jeremy already mentioned, putting a pointer to the compressed ELF 
> image in the bzImage header (and bumping the version number to 2.08) is 
> the right way to go about it.  The compression format (for now, always 
> gzip) can then be identified in the usual way via compression format 
> magic number.
> 
> As I've previously expressed, I'm much happier with this approach than 
> having the compressor portion itself be an ELF image, so I'm happy to 
> see this patch.  However, I think it needs to ride a cycle in -mm, so 
> although I didn't see any problems from a cursory look I might not get a 
> chance to do a detailed review until the merge window is over.

That's good enough for me -- I shall press on...

Cheers,
Ian.

-- 
Ian Campbell

Pascal:
	A programming language named after a man who would turn over
	in his grave if he knew about it.
		-- Datamation, January 15, 1984

--
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/