linux-kernel - Re: [update5] [PATCH] init: bzip2 or lzma -compressed kernels and initrds

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:	Fri, 10 Oct 2008 14:31:12 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alain Knaff <alain@...ff.lu>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [update5] [PATCH] init: bzip2 or lzma -compressed kernels and
 initrds

Alain Knaff wrote:
> H. Peter Anvin wrote:
>> Hi Alain,
>>
>> Are you planning to submit an updated patch any time soon?  If so,
>> please separate the ARM, x86, library and generic portions into separate
>> patches.  It looks like at least some of them already went into ARM,
>> which makes it impractical to include this as a monolithic patch, which
>> it really shouldn't have to be, anyway.
>>
>>     -hpa
> 
> I'll look into it (the split) this weekend, if I'll find the time.
> Should each part be compilable on its own? If so, it might be difficult
> to do the split along the lines outlined above.
> 

Not individually, but part 1 should compile, as should parts 1+2, etc.

This pretty much means the order should be:

1. add library functions
2. generic functionality
3. x86 functionality
4. ARM functionality

Soem of these may be obsolete; I noticed collisions with the ARM tree.

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