mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Roman Zippel <zippel@fh-brandenburg.de>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	dek_ml@konerding.com, linux-kernel@vger.kernel.org,
	nfs@lists.sourceforge.net, mason@suse.com
Subject: Re: [NFS] Re: problems with reiserfs + nfs using 2.4.2-pre4
Date: Tue, 20 Feb 2001 16:16:31 +0100 (CET)	[thread overview]
Message-ID: <14994.35407.280038.934149@charged.uio.no> (raw)
In-Reply-To: <Pine.GSO.4.10.10102201455390.13098-100000@zeus.fh-brandenburg.de>
In-Reply-To: <shslmr11yfs.fsf@charged.uio.no> <Pine.GSO.4.10.10102201455390.13098-100000@zeus.fh-brandenburg.de>

>>>>> " " == Roman Zippel <zippel@fh-brandenburg.de> writes:

     > If I read the source correctly, namespace operation are done
     > with dir file handle + file name. I'm playing with the idea if
     > we could relax the rule, that all dentries must be connected to
     > the root. Inode to dentry lookups are really evil, e.g. the
     > current code ignores that there might be a fs that supports
     > links to dirs (besides that vfs doesn't support that very well
     > either).  What IMO knfsd needs is only a file handle <-> inode
     > operation and as long as the inode is not connected to a dcache
     > entry (i_dentry is empty) it gets a dummy dentry, which is used
     > for further lookups. As soon as a real dentry lookups that
     > inode, we can flush the dummy dentry (small change to
     > d_instantiate()).  This would make it possible to support fs,
     > that can't lookup ".." or it would avoid extra checks for fs,
     > that don't have real ".." dir entries.  All what a fs needs to
     > do is to generate a 16(?) byte cookie, which can be used to
     > find the inode back (with the default to i_ino + i_generation).
     > This is nothing for 2.4, but IMO something that could be tried
     > with 2.5.

Isn't this more or less the default already in 2.4?

If I read the code correctly, we set the dentry d_flag
DCACHE_NFSD_DISCONNECTED on such dummy dentries.  We only force a
lookup of the full path if the inode represents a directory or the
NFSEXP_NOSUBTREECHECK export flag is not set.

It doesn't seem like a major change to delay that full path lookup of
the dentry until nfsd_lookup('..') is actually called (in the case
where the 'subtree_check' flag isn't used).
However, outright banning lookups of '..' by any one filesystem isn't
an option: path lookups are used for a lot more than just
`getcwd'. Imagine for instance trying to follow a relative soft link
across such a filesystem.

Cheers,
  Trond

  parent reply	other threads:[~2001-02-20 15:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-19  0:18 dek_ml
2001-02-19  0:37 ` Neil Brown
2001-02-19  2:56   ` dek_ml
2001-02-19  3:40     ` Neil Brown
2001-02-19 11:23       ` Alan Cox
2001-02-20  0:40         ` Neil Brown
2001-02-20  1:15           ` Chris Mason
2001-02-20  1:34             ` Neil Brown
2001-02-20  1:24           ` Alan Cox
2001-02-20  1:37             ` Neil Brown
2001-02-20  2:11             ` dek_ml
2001-02-20 22:54               ` Brian May
2001-02-20 23:30                 ` Chris Mason
2001-02-20  2:38           ` Roman Zippel
2001-02-20  9:44             ` [NFS] " Trond Myklebust
2001-02-20 14:02               ` Roman Zippel
2001-02-20 15:16               ` Trond Myklebust [this message]
2001-02-20 16:26                 ` Roman Zippel
2001-02-21  3:02             ` Neil Brown
2001-02-21 12:43               ` [NFS] " Trond Myklebust
2001-02-19  1:55 ` Alan Cox
2001-02-19 15:37   ` Chris Mason

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=14994.35407.280038.934149@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dek_ml@konerding.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=neilb@cse.unsw.edu.au \
    --cc=nfs@lists.sourceforge.net \
    --cc=zippel@fh-brandenburg.de \
    /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®