linux-kernel - Re: [0/7] Distributed storage for drivers/staging merge request

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]

Date:	Wed, 14 Jan 2009 03:15:46 +0300
From:	Evgeniy Polyakov <zbr@...emap.net>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Greg KH <greg@...ah.com>, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, dst@...emap.net
Subject: Re: [0/7] Distributed storage for drivers/staging merge request

On Tue, Jan 13, 2009 at 04:12:21PM -0800, Andrew Morton (akpm@...ux-foundation.org) wrote:
> > Hm, then why can't this whole thing just go into fs/dst/ right now?
> > It's self-contained, so there shouldn't be any special "must live in
> > staging" rule for filesystems before adding them.
> > 
> > We take new drivers at almost any point in the release cycle, why should
> > filesystems be any different?
> 
> Well...  the case for merging drivers is usually pretty simple - the
> hardware exists, so we need the driver.
> 
> Whereas the "do we need this" case for new filesystems isn't this simple.

More on this, it is a block device which does not work with hardware.
And yes, question is serious. And you may not believe, but it is not me
to answer this. I'm happy to provide any needed information.
In a nutshell, it is a network block device on really huge steroids.

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