linux-kernel - JFFS2 using 'private' zlib header (was [RFC] LZO de/compression support

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: <231C137C-D0BF-44F7-B2D5-AE610284D00A@cam.ac.uk>
Date:	Tue, 29 May 2007 14:33:51 +0100
From:	Michael-Luke Jones <mlj28@....ac.uk>
To:	Satyam Sharma <satyam.sharma@...il.com>
Cc:	Nitin Gupta <nitingupta910@...il.com>,
	lkml <linux-kernel@...r.kernel.org>, linux-mm-cc@...top.org,
	linuxcompressed-devel@...ts.sourceforge.net,
	Andrew Morton <akpm@...ux-foundation.org>,
	Daniel Hazelton <dhazelton@...er.net>,
	Richard Purdie <richard@...nedhand.com>,
	Bret Towe <magnade@...il.com>, dwmw2@...radead.org
Subject: JFFS2 using 'private' zlib header (was [RFC] LZO de/compression support - take 6)

On 29 May 2007, at 12:27, Satyam Sharma wrote:

> Right, actually, zlib could be switched over to [using a common  
> directory].
> Because zlib_deflate/ and zlib_inflate/ too share a private header
> zutil.h which has unfortunately been stuck into include/linux/ with  
> a big
> /* WARNING: this file should *not* be used by applications. */  
> comment ...

Well, unfortunately zutil.h is currently being used in-kernel by fs/ 
jffs2/compr_zlib.c despite the "WARNING: this file should *not* be  
used by applications" notice.

So moving this header to a truly private location isn't possible  
right now, unfortunately,

Michael-Luke Jones
[added David Whitehouse to cc]
-
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/