linux-kernel - Re: [PATCH 2/4] virtual block device driver (ramzswap)

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: <84144f020909150542k1d62f100ubaef3bb3b1cea592@mail.gmail.com>
Date:	Tue, 15 Sep 2009 15:42:09 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Ed Tomlinson <edt@....ca>
Cc:	Nitin Gupta <ngupta@...are.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Hugh Dickins <hugh.dickins@...cali.co.uk>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	linux-mm-cc@...top.org, Ingo Molnar <mingo@...e.hu>,
	Frédéric Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>, Greg KH <greg@...ah.com>
Subject: Re: [PATCH 2/4] virtual block device driver (ramzswap)

On Tuesday 15 September 2009 03:30:23 you wrote:
>> > So, its extremely difficult to wait for the proper fix.
>>
>> Then make ramzswap depend on !CONFIG_ARM. In any case, CONFIG_ARM bits
>> really don't belong into drivers/block.

On Tue, Sep 15, 2009 at 2:45 PM, Ed Tomlinson <edt@....ca> wrote:
> Problem is that ramzswap is usefull on boxes like the n800/n810...  So this is a bad
> suggestion from my POV.    How about a comment saying this code goes when the
> fix arrives???

Just put the driver in driver/staging until the issue is resolved.
--
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/