All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Christoph Hellwig <hch@infradead.org>
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 13:33:46 -0400	[thread overview]
Message-ID: <1157045626.11347.97.camel@localhost> (raw)
In-Reply-To: <20060831162628.GA23925@infradead.org>

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


  reply	other threads:[~2006-08-31 17:34 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
2006-08-31 17:33     ` Trond Myklebust [this message]
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=1157045626.11347.97.camel@localhost \
    --to=trond.myklebust@fys.uio.no \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spotter@cs.columbia.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.