From: Olaf Kirch <okir@suse.de>
To: linuxkernel@arcor.de
Cc: nfs@lists.sourceforge.net
Subject: Re: several oopses of nfsd in 2.6.16.29
Date: Fri, 1 Dec 2006 10:26:00 +0100 [thread overview]
Message-ID: <20061201092559.GE11918@suse.de> (raw)
In-Reply-To: <20695426.1164960395196.JavaMail.ngmail@webmail13>
On Fri, Dec 01, 2006 at 09:06:35AM +0100, linuxkernel@arcor.de wrote:
> it happened again, but this time without /proc/fs/nfsd mounted. This is getting on my nerves.
> Please see attached the oopses. Now I switched to 2.6.16.33.
It doesn't look like this is necessarily nfsd's fault; this looks more
like memory corruption to me. Something stomped on either the inode or
(less likely) the inode->ops of some file.
I'd suggest building the kernel with slab debugging enabled and
see whether that turns up anything useful.
There's a remote chance this is related to ACLs though, as the
first crash is in an ACL call. Are you using ACLs at all?
Olaf
--
Walks like a duck. Quacks like a duck. Must be a chicken.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-12-01 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 8:06 several oopses of nfsd in 2.6.16.29 linuxkernel
2006-12-01 9:26 ` Olaf Kirch [this message]
[not found] <139134.1164970331572.JavaMail.ngmail@webmail13>
2006-12-01 10:59 ` linuxkernel
-- strict thread matches above, loose matches on Subject: below --
2006-12-06 5:33 Kevin Jamieson
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=20061201092559.GE11918@suse.de \
--to=okir@suse.de \
--cc=linuxkernel@arcor.de \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.