From: "J. Bruce Fields" <bfields@fieldses.org>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
nfsv4@linux-nfs.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [NFSv4] 2.6.23-rc4 oops in nfs4_cb_recall...
Date: Sun, 9 Sep 2007 17:04:00 -0400 [thread overview]
Message-ID: <20070909210400.GA7136@fieldses.org> (raw)
In-Reply-To: <6278d2220709040405i4f816afemb3a44d9cd95f9cc@mail.gmail.com>
> When accessing a directory inode from a single other client, NFSv4
> callbacks catastrophically failed [1] on the NFS server with
> 2.6.23-rc4 (unpatched); clients are both 2.6.22 (Ubuntu Gutsy build).
> Seems not easy to reproduce, since this kernel was running smoothly
> for 7 days on the server.
>
> What information will help track this down, or is there a known
> failure mechanism?
I haven't seen that before.
> I can map stack frames to source lines with objdump, if that helps.
If it's still easy, it might help to figure out exactly where in
xprt_reserve() it died, and why. If we've got some race that can lead
to freeing the client while a callback is in progress, then perhaps this
is on the first dereference of xprt?
--b.
next prev parent reply other threads:[~2007-09-09 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 11:05 [NFSv4] 2.6.23-rc4 oops in nfs4_cb_recall Daniel J Blueman
2007-09-09 21:04 ` J. Bruce Fields [this message]
2007-09-10 14:39 ` Daniel J Blueman
2007-09-13 1:53 ` J. Bruce Fields
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=20070909210400.GA7136@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=daniel.blueman@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfsv4@linux-nfs.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