From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfs_lookup_validate and dud inodes
Date: 30 Oct 2001 23:05:57 +0100 [thread overview]
Message-ID: <shs8zds941m.fsf@susy.uio.no> (raw)
In-Reply-To: <m3zo68rjk7.fsf@quimbies.gnus.org>
In-Reply-To: <m3zo68rjk7.fsf@quimbies.gnus.org>
>>>>> " " == 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
prev parent reply other threads:[~2001-10-30 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 19:53 Lars Magne Ingebrigtsen
2001-10-30 22:05 ` Trond Myklebust [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=shs8zds941m.fsf@susy.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=larsi@gnus.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®