linux-kernel - Re: tip: bzip2/lzma now in tip:x86/setup-lzma

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: <20090302095301.GH20897@elte.hu>
Date:	Mon, 2 Mar 2009 10:53:01 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Alain Knaff <alain@...ff.lu>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Jan Engelhardt <jengelh@...ozas.de>,
	the arch/x86 maintainers <x86@...nel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: tip: bzip2/lzma now in tip:x86/setup-lzma


* Alain Knaff <alain@...ff.lu> wrote:

> Alain Knaff wrote:
> > Alain Knaff wrote:
> >> hmmm, but on a second glance, there seems to be indeed an issue. When
> >> compiling it a _second time_, compilation will "succeed" but produce a
> >> bad kernel because the first attempt left an empty
> >> usr/initramfs_data.cpio.bz2 .
> >>
> >> I'll look into it this evening, probably a case of "bad" failure
> >> recovery in the Makefile.
> >>
> > 
> > Took me slightly longer than promised, attached is the patch.
> > 
> > It changes/fixes three things:
> > 1. Fix a bug in decompress.c : only scanned until the first
> > non-configured compressor (with disastrous result if that was gzip)
> > 2. Fix a bug in gen_initramfs_list.sh : in case of failure, it left
> > indeed an empty output file behind, messing up the next make.
> > 3. Make builtin initramfs compression configurable
> > 
> > Regards,
> > 
> > Alain
> > 
> 
> Any comments about this? Ingo, does it solve the issue with 
> randconfig?

I've reactivated tip:x86/setup-lzma in tip:master and started 
testing it with the problem .config, on the problem test-system. 
The bug is most likely fixed, so consider it queued up for 
2.6.30 unless i report some new issue.

Thanks,

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