Re: bug in nfs in 2.6.18-rc5?
- From: Trond Myklebust <trond.myklebust@xxxxxxxxxx>
- Date: Thu, 31 Aug 2006 13:33:46 -0400
On Thu, 2006-08-31 at 17:26 +0100, Christoph Hellwig wrote:
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.
Good. I fully agree that this is preferable.
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- bug in nfs in 2.6.18-rc5?
- From: Shaya Potter
- Re: bug in nfs in 2.6.18-rc5?
- From: Trond Myklebust
- Re: bug in nfs in 2.6.18-rc5?
- From: Christoph Hellwig
- bug in nfs in 2.6.18-rc5?
- Prev by Date: Re: [patch 0/6] RFC: fault-injection capabilities (v2)
- Next by Date: Re: [PATCH 01/16] GFS2: Core header files
- Previous by thread: Re: bug in nfs in 2.6.18-rc5?
- Next by thread: Re: bug in nfs in 2.6.18-rc5?
- Index(es):