From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Dave Carrigan <dave@rudedog.org>, linux-kernel@vger.kernel.org
Subject: Re: Kernel crash with knfsd
Date: Thu, 27 Dec 2001 17:50:45 +0100 [thread overview]
Message-ID: <3C2B5165.B6A6CEC1@loewe-komp.de> (raw)
In-Reply-To: <87heqdanpx.fsf@pdaverticals.com> <15402.12470.768116.337927@notabene.cse.unsw.edu.au>
Neil Brown schrieb:
>
> On December 26, dave@rudedog.org wrote:
> > (I am not subscribed, so please CC any response to me)
> >
> > I am having the following problem:
> >
> > Sometimes, when my wife's laptop comes out of suspend mode, it causes my
> > nfs server to lock up hard -- I have to hit the reset button. Even after
> > I reset the server, it will just lock up again a few seconds after knfsd
> > starts, as long as the laptop is still on the net. If I suspend the
> > laptop, then start the server, it will start fine, and I can usually
> > unsuspend the laptop after that without problems. Up until yesterday,
> > there was never anything in the logs.
>
> snip
>
> > Dec 25 14:51:35 pern kernel: Call Trace: [nfsd_findparent+52/256] [find_fh_dentry+558/820] [fh_verify+508/988] [reschedule_idle+98/540] [nfsd_lookup+114/1016]
> > Dec 25 14:51:35 pern kernel: [nfsd3_proc_lookup+212/224] [nfsd_dispatch+211/416] [svc_process+653/1240] [nfsd+503/808] [kernel_thread+40/56]
> > Dec 25 14:51:35 pern kernel:
> > Dec 25 14:51:35 pern kernel: Code: Bad EIP value.
>
> snip
>
> >
> > The server is running 2.4.16 with XFS patches. The nfs-exported
> > directories are both xfs and rieserfs. The laptop runs kernel autofs,
>
> I have had several reports of XFS triggering an oops early in
> nfsd_findparent. I thought that the problem has been fixed by
> 2.4.16....
>
> Can you send me a copy of nfsd_findparent out of fs/nfsd/nfsfh.c
> in the source tree that you are using?
>
There was a fix in 2.4.3 for lookup("..") failing.
This oops seems to me the one I am waiting to happen again for 4 weeks now :-(
The i_node->op->something is NULL, I guess.
prev parent reply other threads:[~2001-12-27 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-26 17:35 Kernel crash with knfsd Dave Carrigan
2001-12-26 18:52 ` Alan Cox
2001-12-26 20:19 ` Neil Brown
2001-12-27 16:50 ` Peter Wächtler [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=3C2B5165.B6A6CEC1@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=dave@rudedog.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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