On Sat, 22 Jan 2011, Namhyung Kim wrote:
> dcache-locking.txt is not exist any more, and the path was not
> correct anyway. Fix it.
>
> Signed-off-by: Namhyung Kim <namhyung@xxxxxxxxx>
> ---
> fs/dcache.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/dcache.c b/fs/dcache.c
> index 9f493ee4dcba..56be05ef4fe3 100644
> --- a/fs/dcache.c
> +++ b/fs/dcache.c
> @@ -1779,7 +1779,7 @@ struct dentry *__d_lookup_rcu(struct dentry *parent, struct qstr *name,
> * false-negative result. d_lookup() protects against concurrent
> * renames using rename_lock seqlock.
> *
> - * See Documentation/vfs/dcache-locking.txt for more details.
> + * See Documentation/filesystems/path-lookup.txt for more details.
> */
> hlist_bl_for_each_entry_rcu(dentry, node, &b->head, d_hash) {
> struct inode *i;
> @@ -1899,7 +1899,7 @@ struct dentry *__d_lookup(struct dentry *parent, struct qstr *name)
> * false-negative result. d_lookup() protects against concurrent
> * renames using rename_lock seqlock.
> *
> - * See Documentation/vfs/dcache-locking.txt for more details.
> + * See Documentation/filesystems/path-lookup.txt for more details.
> */
> rcu_read_lock();
Doesn't seem to be present in linux-next as of today. I have picked that
up.
--
Jiri Kosina
SUSE Labs, Novell Inc.
--
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
