Thread (4 messages) 4 messages, 2 authors, 2011-01-06

nameidata data structure again

From: mohit verma <hidden>
Date: 2011-01-06 17:42:26

thank you rajat.

On Thu, Jan 6, 2011 at 6:10 PM, Rajat Sharma [off-list ref] 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 [off-list ref] wrote:
quoted

---------- Forwarded message ----------
From: mohit verma <redacted>
Date: Thu, Jan 6, 2011 at 5:10 PM
Subject: nameidata data structure again
To: kernelnewbies <redacted>


hi folks,


we have qstr data structure part in nameidata structure in name
resolution.
quoted
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
quoted
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 
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help