linux-kernel - Re: [PATCH -mm 0/5] LZO and swap write failure patches for -mm

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] [day] [month] [year] [list]

Message-Id: <1181033802.6180.11.camel@localhost.localdomain>
Date:	Tue, 05 Jun 2007 09:56:42 +0100
From:	Richard Purdie <rpurdie@...nedhand.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Nitin Gupta <nitingupta910@...il.com>,
	Adrian Bunk <bunk@...sta.de>,
	Daniel Hazelton <dhazelton@...er.net>,
	LKML <linux-kernel@...r.kernel.org>,
	Hugh Dickins <hugh@...itas.com>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH -mm 0/5] LZO and swap write failure patches for -mm

On Mon, 2007-06-04 at 22:50 -0700, Andrew Morton wrote:
> I'd say go with the cleanups.  The code I've seen is going to be quite
> unmaintainable by any kernel developer.
> 
> Any fixes which come from upstream can be trivially applied by taking the
> diffs against the version of upstream we started with and manually applying
> them to our version.  If the diffs are too large and complex for that then
> a) we shouldn't be merging the code in its current state anyway and b) with
> the code as-is we couldn't effectively review or changelog those diffs, so
> we shouldn't apply them.
> 
> So just fork it and freeze it.

Ok, thanks for the decision.

Since I don't have too much faith in what Nitin has done with it, I'll
produce a version myself. In theory we should end up with identical code
so will be a sanity check of Nitin's code if nothing else.

Cheers,

Richard


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