Question about dcache_lock

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello.


Q1:
Is dcache_lock needed for referring
dentry->d_parent and dentry->d_name?
I'm using a d_path()-like function
that traverses up to the root of the dentry.
http://tomoyo.sourceforge.jp/cgi-bin/lxr/source/include/linux/syaoran.h#L599
Is dcache_lock needed for this function?


Q2:
Is dcache_lock still needed for referring only dentry->d_parent?
I found the following comment in http://lkml.org/lkml/2005/3/10/186 .
Is this comment right?
> +	/* FIXME? I think there is no need to use dget_parent or
> +	   to take dcache_lock here, because dentry->d_parent never
> +	   changes and the dentry holds a reference to its parent,
> +	   and dentry->d_parent holds a reference to
> +	   dentry->d_d_parent->d_inode. Right??? -AJR 2004.11.05 */


Regards.
--
  Tetsuo Handa
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux