From: Jeff Layton <jlayton@redhat.com>
To: Patrick Donnelly <pdonnell@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: [RFC PATCH] client: don't use special inode for /..
Date: Wed, 10 Aug 2016 16:30:05 -0400 [thread overview]
Message-ID: <1470861005.2694.12.camel@redhat.com> (raw)
In-Reply-To: <CA+2bHPYjYPRn99e3nCTjED6c89MnD_Eih_27z_J1=b4_CtLqOg@mail.gmail.com>
On Wed, 2016-08-10 at 16:08 -0400, Patrick Donnelly wrote:
> On Wed, Aug 10, 2016 at 12:30 PM, Jeff Layton <jlayton@redhat.com>
> wrote:
> >
> > The CEPH_INO_DOTDOT thing is quite strange. Under most OS (Linux
> > included), the parent of the root is itself. IOW, at the root, '.'
> > and
> > '..' refer to the same inode.
> >
> > Change the ceph client to do the same, as this allows users to get
> > valid stat info for '..', as well as elimnating some special-
> > casing.
> >
> > Signed-off-by: Jeff Layton <jlayton@redhat.com>
>
> Don't forget Client::_lookup:
>
> if (dname == "..") {
> if (dir->dn_set.empty())
> r = -ENOENT;
> else
> *target = dir->get_first_parent()->dir->parent_inode; //dirs
> can't be hard-linked
> goto done;
> }
>
> Otherwise LGTM.
>
Ahh, thanks. So will dir->dn_set.empty() be true at the root? If so,
then something like the patch below?
Note that this patch is not strictly necessary, but it does simplify
some other changes that I have queued up:
diff --git a/src/client/Client.cc b/src/client/Client.cc
index 5ab0ace4d3df..287baaf20536 100644
--- a/src/client/Client.cc
+++ b/src/client/Client.cc
@@ -5924,7 +5924,7 @@ int Client::_lookup(Inode *dir, const string& dname, int mask,
if (dname == "..") {
if (dir->dn_set.empty())
- r = -ENOENT;
+ *target = dir;
else
*target = dir->get_first_parent()->dir->parent_inode; //dirs can't be hard-linked
goto done;
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2016-08-10 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 16:30 [RFC PATCH] client: don't use special inode for / Jeff Layton
2016-08-10 20:08 ` Patrick Donnelly
2016-08-10 20:30 ` Jeff Layton [this message]
2016-08-10 20:46 ` Patrick Donnelly
2016-08-10 21:06 ` Jeff Layton
2016-08-10 21:15 ` Patrick Donnelly
2016-08-10 22:21 ` Jeff Layton
2016-08-11 1:31 ` Jeff Layton
2016-08-10 21:23 ` Sage Weil
2016-08-10 21:52 ` Jeff Layton
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=1470861005.2694.12.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=pdonnell@redhat.com \
/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.