From: "J. R. Okajima" <hooanon05@yahoo.co.jp>
To: Nick Piggin <npiggin@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: vfs-scale, nd->inode after __do_follow_link()
Date: Fri, 14 Jan 2011 13:41:03 +0900 [thread overview]
Message-ID: <9551.1294980063@jrobl> (raw)
In-Reply-To: <AANLkTinXPOSxHPtffqe3m5MWppDfr6kFVMsd6k7-dkic@mail.gmail.com>
Nick Piggin:
> > Isn't it path.dentry->d_inode instead of nd.inode?
:::
> It should be the inode we followed, rather than the inode of the
> new path, I think.
In __do_follow_link(), path.dentry is what we followed, isn't it?
__do_follow_link()
{
struct dentry *dentry = path->dentry;
;;;
*p = dentry->d_inode->i_op->follow_link(dentry, nd);
;;;
J. R. Okajima
next prev parent reply other threads:[~2011-01-14 4:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 2:10 vfs-scale, nd->inode after __do_follow_link() J. R. Okajima
2011-01-14 2:33 ` J. R. Okajima
2011-01-14 4:09 ` Nick Piggin
2011-01-14 4:09 ` Nick Piggin
2011-01-14 4:41 ` J. R. Okajima [this message]
2011-01-14 5:28 ` Al Viro
2011-01-14 5:38 ` J. R. Okajima
2011-01-14 5:40 ` J. R. Okajima
2011-01-14 8:40 ` Nick Piggin
2011-01-14 9:17 ` Sedat Dilek
2011-01-14 9:17 ` Sedat Dilek
2011-01-14 23:34 ` J.H.
2011-01-15 1:20 ` [Ocfs2-devel] " J.H.
2011-01-15 18:16 ` Nick Piggin
2011-01-14 12:54 ` J. R. Okajima
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=9551.1294980063@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.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.