Re: nfs_lookup_validate and dud inodes

Trond Myklebust (trond.myklebust@fys.uio.no)
30 Oct 2001 23:05:57 +0100


>>>>> " " == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> [larsi@quimbies ~]$ ls -l /tftpboot/sparky/lib/libe2p.so.2*
> lrwxrwxrwx 1 root root 13 Oct 30 20:23
> /tftpboot/sparky/lib/libe2p.so.2 -> libe2p.so.2.3 -rw-r--r-- 1
> root root 13400 Sep 22 17:15 /tftpboot/sparky/lib/libe2p.so.2.3

> So the error message is when trying to access the symlink.

<snip>

> Is this a known bug?

Known and fixed in the 2.2.20-pre series. It's just that the symlink
code in 2.2.19 doesn't call nfs_revalidate_inode() in order to verify
data cache consistency.

Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/