linux-kernel - Re: [PATCH, RFC/T] Fix handling of write failures to swap devices

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: <1161941737.5019.100.camel@localhost.localdomain>
Date:	Fri, 27 Oct 2006 10:35:37 +0100
From:	Richard Purdie <rpurdie@...nedhand.com>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	kernel list <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH, RFC/T] Fix handling of write failures to swap devices

On Fri, 2006-10-27 at 18:22 +1000, Nick Piggin wrote:
> This is the right approach to handling swap write errors. However, you need
> to cut down on the amount of code duplication.

I've just looked at this and there isn't that much code duplicated, just
a couple of big comment blocks which make it look like that. Those
sections are similar in spirit but have been modified to work under
different circumstances. Having looked again, I don't think its worth
trying to merge them as it will become too unreadable.

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/