nameidata data structure again

nameidata data structure again

[mohit verma]

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*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110106/6f29d12c/attachment.html 

Fwd: nameidata data structure again

[mohit verma]

---------- 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*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110106/43ab47f5/attachment.html 

nameidata data structure again

[Rajat Sharma]

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
>
>

nameidata data structure again

[mohit verma]

thank you rajat.

On Thu, Jan 6, 2011 at 6:10 PM, Rajat Sharma <fs.rajat@gmail.com> wrote:

> 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
> >
> >
>



-- 
........................
*MOHIT VERMA*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110106/3c7eeb58/attachment.html