linux-kernel - Re: [PATCH] Allow userspace block device implementation

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090727142536.465799aa@lxorguk.ukuu.org.uk>
Date:	Mon, 27 Jul 2009 14:25:36 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Zachary Amsden <zamsden@...hat.com>, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, axboe@...nel.dk, hch@...radead.org,
	akpm@...ux-foundation.org, Paul.Clements@...eleye.com,
	tytso@....edu, Tejun Heo <tj@...nel.org>,
	miklos <miklos@...redi.hu>
Subject: Re: [PATCH] Allow userspace block device implementation

> Somehow this made me think of FUSE/CUSE... should this be named aBUSE?
> Oh wait it is :-), what I'm after is I guess is, can we share some of
> the FUSE/CUSE code?

It reminds me of the existing and perfectly functional network block
device (nbd) we already have and which has also been present for years.

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