From: Shaya Potter <spotter@cs.columbia.edu>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, unionfs@fsl.cs.sunysb.edu
Subject: bug in nfs in 2.6.18-rc5?
Date: Thu, 31 Aug 2006 10:54:07 -0400 [thread overview]
Message-ID: <44F6F80F.1000202@cs.columbia.edu> (raw)
so I'm trying to use unionfs, cachefs and nfs, as cachefs is 2.6.18-rc5
right now, thats what I'm testing, but I hit an oops.
basically unionfs's lookup does a "lookup_one_len()" on the underlying fs.
lookup_one_len() calls __lookup_hash()
__lookup_hash() is called as "__lookup_hash(&this, base, NULL)"
now that NULL is important. that's the nameidata entry of __lookup_hash()
__lookup_hash() ends up calling the underlying fs's lookup op, i.e.
nfs_lookup()
nfs_lookup() calls nfs_reval_fsid(nd->mnt, dir, &fhandle, &fattr);
see the bug? :)
This doesn't seem like a unionfs bug, as one should be able to call
lookup_one_len() on an NFS fs.
next reply other threads:[~2006-08-31 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 14:54 Shaya Potter [this message]
2006-08-31 15:20 ` bug in nfs in 2.6.18-rc5? 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
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=44F6F80F.1000202@cs.columbia.edu \
--to=spotter@cs.columbia.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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