To: pmarques@grupopie.com
CC: jgarzik@pobox.com, axboe@suse.de, neilb@suse.de,
       linux-kernel@vger.kernel.org
In-reply-to: <E1EZpTU-0001KK-00@dorka.pomaz.szeredi.hu> (message from Miklos
	Szeredi on Wed, 09 Nov 2005 13:54:48 +0100)
Subject: Re: userspace block driver?
References: <4371A4ED.9020800@pobox.com> <17265.42782.188870.907784@cse.unsw.edu.au> <4371A944.6070302@pobox.com> <20051109075455.GN3699@suse.de> <4371ACE6.7010503@pobox.com> <4371EEBA.2080706@grupopie.com> <E1EZpTU-0001KK-00@dorka.pomaz.szeredi.hu>
Message-Id: <E1EZqZK-0001RV-00@dorka.pomaz.szeredi.hu>
From: Miklos Szeredi <miklos@szeredi.hu>
Date: Wed, 09 Nov 2005 15:04:54 +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 831
Lines: 22

> 
> That got me thinking... theoretically we should be able to do a FUSE 
> server that served a single file that could be used by a loopback 
> device, couldn't we?
> 
> IIRC, Miklos Szeredi tried hard to avoid the deadlock scenarios that nbd 
> suffers from in FUSE, but I don't know if it would stand being called by 
> the loopback device.

N.B. though FUSE itself is free of deadlocks, as soon as you put
something on top of it which has asyncronous page writeback it will
not be safe anymore.

So the issues with NBD will still be there if you loopback mount a
fuse file.

Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/