From: Matthias-Christian Ott <matthias.christian@tiscali.de>
To: Der Herr Hofrat <der.herr@hofr.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: proc path_walk glitch ?
Date: Sun, 20 Feb 2005 22:11:03 +0100 [thread overview]
Message-ID: <4218FCE7.1040403@tiscali.de> (raw)
In-Reply-To: <200502202009.j1KK9um25139@hofr.at>
Der Herr Hofrat wrote:
>HI !
>
> I noticed a slight proc filesystem strangness in the 2.4.2X and 2.6.X
> (atleast up to 2.6.8). Assuming that process 8655 exists and is running
> long enough (ls -lR / or so)
>
>cd /proc/8655
>kill -9 8655
>ls
>/usr/bin/ls: .: Stale NFS file handle
>
>open(".", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ESTALE (Stale NFS file handle) from fs/namei.c -> link_path_walk :
>
>int fastcall link_path_walk(const char * name, struct nameidata *nd)
>{
> struct dentry *dentry;
> struct inode *inode;
> int err;
> unsigned int lookup_flags = nd->flags;
>
> while (*name=='/')
> name++;
> if (!*name)
> goto return_reval;
> ...
>
>return_reval:
> /*
> * We bypassed the ordinary revalidation routines.
> * Check the cached dentry for staleness.
> */
> dentry = nd->dentry;
> if (dentry && dentry->d_op && dentry->d_op->d_revalidate) {
> err = -ESTALE;
> if (!dentry->d_op->d_revalidate(dentry, 0)) {
> d_invalidate(dentry);
> break;
> }
> }
>
>
> Why does return_reval return -ESTALE instead of -ENOENT here - might need an
>extra check on what filesystem this is working on ?
>
>/usr/bin/ls: .: no such file or directory
>
> would seem more meaningfull to me when I find it in a logfile.
>
>thx !
>hofrat
>-
>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/
>
>
>
Does it happen in 2.6.10 or are you sing 2.6.8?
Matthias-Christian Ott
next prev parent reply other threads:[~2005-02-20 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 20:09 proc path_walk glitch ? Der Herr Hofrat
2005-02-20 21:11 ` Matthias-Christian Ott [this message]
[not found] <fa.f4pcrfo.f22jh6@ifi.uio.no>
2005-02-20 22:14 ` Bodo Eggert
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=4218FCE7.1040403@tiscali.de \
--to=matthias.christian@tiscali.de \
--cc=der.herr@hofr.at \
--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