linux-kernel - Re: fastboot: unpacking initramfs faster

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]

Message-Id: <1238068631.12756.23.camel@andreas-desktop>
Date:	Thu, 26 Mar 2009 12:57:11 +0100
From:	Andreas Robinson <andr345@...il.com>
To:	Bodo Eggert <7eggert@....de>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: fastboot: unpacking initramfs faster

On Thu, 2009-03-26 at 12:26 +0100, Bodo Eggert wrote:
> On Thu, 26 Mar 2009, Andreas Robinson wrote:
> > On Tue, 2009-03-24 at 23:11 +0100, Bodo Eggert wrote:
[snip]
> > > Why not make a new set? http://7eggert.dyndns.org:8080/l/bgz.tar.gz
> > 
> > Hmm, well if you think there is a chance of it being accepted, then
> > sure! I'll cook something up, but will be looking to use LZO first since
> > it's a bit faster to begin with.
> 
> It's small enough, and now I've updated it to support lzo and put a
> license into the files.

The file permissions are wrong, I'm not allowed to download it.

> Thinking about it: It's now very kernel-specific, other users might like a
> block signature to make it robust against errors - e.g. in the middle of a
> .tar.bgz file. I think I'll change that soon and put 0x55aa in front of
> each block.

I think we'll want an optional checksum of the compressed data.
Suppose bit 32 in the compressed block size field is set, the next field
is the block's Adler32 checksum.
(the adler32 source is in include/linux/zutil.h)

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