From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Shaya Potter <spotter@cs.columbia.edu>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
unionfs@fsl.cs.sunysb.edu
Subject: Re: bug in nfs in 2.6.18-rc5?
Date: Thu, 31 Aug 2006 17:26:28 +0100 [thread overview]
Message-ID: <20060831162628.GA23925@infradead.org> (raw)
In-Reply-To: <1157040230.11347.31.camel@localhost>
On Thu, Aug 31, 2006 at 12:03:50PM -0400, Trond Myklebust wrote:
> If we're to provide the ability for unionfs to use lookup_one_len() on
> NFS, then we will have to error out whenever we hit a case where we
> should be creating a new mountpoint. Is that acceptable?
Not at all. unionfs will have to pass down proper lookup intents.
The ecryptfs developers have started looking into making that work
with stackable filesystems, and the unionfs developers should follow
that effort.
next prev parent reply other threads:[~2006-08-31 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 14:54 bug in nfs in 2.6.18-rc5? Shaya Potter
2006-08-31 15:20 ` Shaya Potter
2006-08-31 16:03 ` Trond Myklebust
2006-08-31 16:24 ` Shaya Potter
2006-08-31 16:43 ` Trond Myklebust
2006-08-31 16:26 ` Christoph Hellwig [this message]
2006-08-31 17:33 ` Trond Myklebust
2006-08-31 16:27 ` Christoph Hellwig
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=20060831162628.GA23925@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spotter@cs.columbia.edu \
--cc=trond.myklebust@fys.uio.no \
--cc=unionfs@fsl.cs.sunysb.edu \
/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