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  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, 03 Jan 2010 00:55:55 +0000
From:	Phillip Lougher <>
To:	Randy Dunlap <>
CC:	Stephen Rothwell <>,, LKML <>,
	Michal Marek <>, akpm <>
Subject: Re: [PATCH -next] libs: force lzma_wrapper to be retained

Randy Dunlap wrote:
> From: Randy Dunlap <>
> When CONFIG_SQUASHFS=m and CONFIG_DECOMPRESS_LZMA=m, decompress_lzma
> is built but then discarded from the library because no built-in code
> uses it, so change it from a lib- to an obj- to force it to be kept
> in the library.
> ERROR: "unlzma" [fs/squashfs/squashfs.ko] undefined!

Thanks for fixing this, I should have spotted it in my various
config tests but didn't.  I could add this to my squashfs-next patches
to stop the linux-next tree breakage, however, should it go into
Michal's kbuild -next tree instead?

This patch raises a small additional issue, why is DECOMPRESS_LZMA
(and DECOMPRESS_GZIP/DECOMPRESS_BZIP2) and defined as tristate?
None of the above compressors can be built as modules.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists