From: Pavel Machek <pavel@ucw.cz>
To: Miklos Szeredi <Miklos.Szeredi@eth.ericsson.se>
Cc: azz@us-lot.org, linux-kernel@vger.kernel.org
Subject: Re: Userspace filesystems (WAS: Encrypted Filesystem)
Date: Fri, 30 Jan 2004 18:06:10 +0100 [thread overview]
Message-ID: <20040130170610.GB625@elf.ucw.cz> (raw)
In-Reply-To: <200401281350.i0SDo2I03247@duna48.eth.ericsson.se>
Hi!
> 2) This one is harder to get rid of, especially because I don't want
> to delve into the technical merits of one or the other (I'd be a
> bit biased). But I have compared both the kernel interface and
> the library API of LUFS and FUSE and they are very similar. And
> that is a good thing, because it makes possible to support LUFS
> filesystems with the FUSE kernel module and vica versa.
Jean-Luc wrote:
> app wants to read data from a file ->
> userspace application requires memory allocation to provide this data ->
> VM tries to write out dirty data associated with the Coda mountpoint ==
> deadlock
How do you solve this one?
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-01-30 17:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 17:46 Encrypted Filesystem Michael A Halcrow
2004-01-26 19:06 ` Mark Borgerding
2004-01-26 21:04 ` Felipe Alfaro Solana
2004-01-30 17:01 ` Pavel Machek
2004-01-27 0:06 ` jw schultz
2004-01-27 0:43 ` Adam Sampson
2004-01-27 1:42 ` Andy Isaacson
2004-01-27 22:01 ` Jan Harkes
2004-01-27 22:16 ` Jean-Luc Cooke
2004-01-28 13:50 ` Userspace filesystems (WAS: Encrypted Filesystem) Miklos Szeredi
2004-01-30 17:06 ` Pavel Machek [this message]
2004-02-02 9:42 ` Miklos Szeredi
2004-02-02 15:19 ` Pavel Machek
2004-02-02 15:36 ` Nikita Danilov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040130170610.GB625@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Miklos.Szeredi@eth.ericsson.se \
--cc=azz@us-lot.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®