From: Chuck Ebbert <cebbert@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6.23-rc3] NFSv4 client oops
Date: Wed, 15 Aug 2007 18:30:33 -0400 [thread overview]
Message-ID: <46C37E89.6030204@redhat.com> (raw)
In-Reply-To: <46C37958.7000401@garzik.org>
On 08/15/2007 06:08 PM, Jeff Garzik wrote:
> While upgrading nfs-utils on my NFSv4 file server (F7 x86-64
> 2.6.23-rc3), I got an oops on the NFSv4 client (FC6 x86-64 2.6.23-rc3),
> and communications stopped.
>
> I rebooted the client, and everything was fine again. Then, on the
> server, I removed an extra nfs-utils package left over from FC6, causing
> the nfs daemons to be restarted. Another oops.
>
> So it seems like whatever Fedora does during an nfs-utils upgrade __on
> the server__ is causing a remote oops __on the client__.
>
> NFSv4 client kernel config also attached.
>
> Never seen this problem before, but then again, never did a remote OS
> upgrade of the fileserver while running NFSv4 before.
>
Can you post disassembly of the encode_open() function? The x86_64 code
dump doesn't give enough preceding code to diagnose the problem.
next prev parent reply other threads:[~2007-08-15 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 22:08 [2.6.23-rc3] NFSv4 client oops Jeff Garzik
2007-08-15 22:30 ` Chuck Ebbert [this message]
2007-08-17 11:55 ` Trond Myklebust
2007-08-27 14:01 ` Trond Myklebust
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=46C37E89.6030204@redhat.com \
--to=cebbert@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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.