From: fs.rajat@gmail.com (Rajat Sharma)
To: kernelnewbies@lists.kernelnewbies.org
Subject: nameidata data structure again
Date: Thu, 6 Jan 2011 18:10:35 +0530 [thread overview]
Message-ID: <AANLkTimpgcQAFbydUyuS6E+YOUcU42R1j1ToOYfmau7q@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=5J4WXiKzW1hDmFoS4MiFKYTsQUA1g5Cw20hCT@mail.gmail.com>
Hi Mohit,
Please refer to ULK 3rd edition Section 12.5 pathname lookup, it says:
struct qstr last Last component of the pathname (used
when the LOOKUP_PARENT flag is set)
so if LOOKUP_PARENT is set, last refers to the last name components,
e.g. in /a/b/c it reference to c while path->dentry->qstr will refer
to b because you intended to lookup parent not the last component.
Note that path is an output parameter while last is input parameter.
Rajat
On Thu, Jan 6, 2011 at 5:18 PM, mohit verma <mohit89mlnc@gmail.com> wrote:
>
>
> ---------- Forwarded message ----------
> From: mohit verma <mohit89mlnc@gmail.com>
> Date: Thu, Jan 6, 2011 at 5:10 PM
> Subject: nameidata data structure again
> To: kernelnewbies <kernelnewbies@nl.linux.org>
>
>
> hi folks,
>
>
> we have qstr data structure part in nameidata structure in name resolution.
> so it may work like this :
>
> ?nameidata->path->dentry->qstr.
>
> it? is the real name component in a? path name for that directory ro file (i
> think so).
>
> so what is? the need of having another qstr like:
>
> namidata->qstr (ie. last)
>
>
> in nameidata structure.
> sorry ,it may seem? foolish to u guys but i ............
>
> thanks in advance.
> --
> ........................
> MOHIT VERMA
>
>
>
> --
> ........................
> MOHIT VERMA
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
next prev parent reply other threads:[~2011-01-06 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 11:40 nameidata data structure again mohit verma
2011-01-06 11:48 ` Fwd: " mohit verma
2011-01-06 12:40 ` Rajat Sharma [this message]
2011-01-06 17:42 ` mohit verma
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=AANLkTimpgcQAFbydUyuS6E+YOUcU42R1j1ToOYfmau7q@mail.gmail.com \
--to=fs.rajat@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).