linux-kernel - 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]

Date:	Sun, 04 Jan 2009 15:58:23 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alain Knaff <alain@...ff.lu>,
	the arch/x86 maintainers <x86@...nel.org>
CC:	linux-kernel@...r.kernel.org
Subject: tip: bzip2/lzma now in tip:x86/setup-lzma

I have pulled the x86 parts of the bzip2/lzma patchset into
tip:x86/setup-lzma.  I would appreciate it if you could look at it and
make sure it looks sane.  I have not added the ARM portions (patch 4),
since those should go via the ARM tree, nor the capstone patch 5, which
can only be added after the old code is removed from *all* remaining
architectures.

Ingo: this *will* break your randconfig testing if you have machines
where the lzma(1) utility isn't installed!

The shortlog looks like:

Alain Knaff (3):
      bzip2/lzma: library support for gzip, bzip2 and lzma decompression
      bzip2/lzma: config and initramfs support for bzip2/lzma 	decompression
      bzip2/lzma: x86 kernel compression support

H. Peter Anvin (3):
      bzip2/lzma: use a table to search for initramfs compression formats
      bzip2/lzma: handle failures from bzip2 and lzma correctly
      bzip2/lzma: make config machinery an arch configurable

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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