From: Hanna Linder <hannal@us.ibm.com>
To: Jon Miles <jon@cybah.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: [bug] 2.4.18 Call Trace: [link_path_walk+889/2008] [path_walk+26/28] [open_namei+131/1596] [filp_open+59/92] [sys_open+54/204] [system_call+51/56]
Date: Tue, 10 Jun 2003 12:22:00 -0700 [thread overview]
Message-ID: <46010000.1055272920@w-hlinder> (raw)
In-Reply-To: <1055267308.18284.260.camel@fusion.local>
--On Tuesday, June 10, 2003 06:48:29 PM +0100 Jon Miles <jon@cybah.co.uk> wrote:
> I'm not sure if I should be sending an oops from a Debian 2.4.18 kernel
> or not? ... this may be useful. I'm not subscribed to the list.
>
> kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000081
> kernel: Call Trace: [link_path_walk+889/2008] [path_walk+26/28] [open_namei+131/1596] [filp_open+59/92] [sys_open+54/204]
>
> These patches were applied:
>
> * NFS client seekdir patch
> http://www.fys.uio.no/~trondmy/src/
How well have the changes to link_path_walk() included in the 2.4.18 patches
listed above been tested? Has Al Viro reviewed them? They look suspect to me
as they are in the function causing the problem:
> +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;
> + }
> + }
Just my $0.02
Hanna
prev parent reply other threads:[~2003-06-10 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 17:48 Jon Miles
2003-06-10 19:22 ` Hanna Linder [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=46010000.1055272920@w-hlinder \
--to=hannal@us.ibm.com \
--cc=jon@cybah.co.uk \
--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®