From: Nix <nix@esperi.org.uk>
To: "Myklebust\, Trond" <Trond.Myklebust@netapp.com>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
"Oleg Nesterov" <oleg@redhat.com>,
"Jeff Layton" <jlayton@redhat.com>,
"NFS list" <linux-nfs@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"dhowells@redhat.com" <dhowells@redhat.com>
Subject: Re: [3.10.4] NFS locking panic, plus persisting NFS shutdown panic from 3.9.*
Date: Tue, 06 Aug 2013 21:46:04 +0100 [thread overview]
Message-ID: <87pptqsg37.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <1375729975.7337.39.camel@leira.trondhjem.org> (Trond Myklebust's message of "Mon, 5 Aug 2013 19:12:55 +0000")
On 5 Aug 2013, Trond Myklebust uttered the following:
> Yes. This scheme will only work if we make sure that host->h_rpcclnt is
> initialised at mount time. Here is a v2 patch that should do the right
> thing.
Confirmed, that fixes it! I'll try your shutdown crash fix next.
--
NULL && (void)
next prev parent reply other threads:[~2013-08-06 20:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 15:40 [3.10.4] NFS locking panic, plus persisting NFS shutdown panic from 3.9.* Nix
2013-08-05 12:44 ` Jeff Layton
2013-08-05 14:48 ` Nix
2013-08-05 15:04 ` Jeff Layton
2013-08-05 15:11 ` Jeff Layton
2013-08-05 15:50 ` Nix
2013-08-05 16:15 ` Myklebust, Trond
2013-08-05 17:37 ` Jeff Layton
2013-08-05 18:18 ` Myklebust, Trond
2013-08-05 18:33 ` Jeff Layton
2013-08-06 2:21 ` Myklebust, Trond
2013-08-06 9:24 ` Jeff Layton
2013-08-07 10:18 ` Nix
2013-08-07 15:27 ` Myklebust, Trond
2013-08-07 15:27 ` Myklebust, Trond
2013-08-07 21:01 ` Nix
2013-08-07 21:09 ` Myklebust, Trond
2013-08-07 21:09 ` Myklebust, Trond
2013-08-05 18:33 ` Nix
2013-08-05 19:12 ` Myklebust, Trond
2013-08-06 20:46 ` Nix [this message]
2013-08-05 16:21 ` Jeff Layton
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=87pptqsg37.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=Trond.Myklebust@netapp.com \
--cc=dhowells@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=toralf.foerster@gmx.de \
/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.