From: Nix <nix@esperi.org.uk>
To: "Myklebust\, Trond" <Trond.Myklebust@netapp.com>
Cc: "Jeff Layton" <jlayton@redhat.com>,
"Toralf Förster" <toralf.foerster@gmx.de>,
"Oleg Nesterov" <oleg@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: Wed, 07 Aug 2013 22:01:25 +0100 [thread overview]
Message-ID: <87iozhmd0a.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <1375889252.6488.1.camel@leira.trondhjem.org> (Trond Myklebust's message of "Wed, 7 Aug 2013 15:27:31 +0000")
On 7 Aug 2013, Trond Myklebust said:
> On Wed, 2013-08-07 at 11:18 +0100, Nix wrote:
>> On 6 Aug 2013, Trond Myklebust verbalised:
>> > True. How about something like the following instead. Note the change to
>> > the original patch...
>>
>> Well, with those applied I could reboot without a panic for the first
>> time since 3.8.x: looking good. I'll give it a reboot or two with a
>> system that's not hot from booting though.
>
> Could you please also try applying only the 1/2 patch, to see if that
> suffices to quell the shutdown panic?
It doesn't suffice. I see this severely truncated oops:
[ 115.799092] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
[ 115.800284] IP: [<ffffffff81165ec6>] path_init+0x11c/0x36f
[ 115.801463] PGD 0
[ 115.802625] Oops: 0000 [#1] PREEMPT SMP
[ 115.803805] Modules linked in: [last unloaded: microcode]
[ 115.804995] CPU: 3 PID: 1191 Comm: sleep Not tainted 3.10.5-05317-g3c9f6fa-dirty #2
[ 115.806207] Hardware name: System manufacturer System Product Name/P8H61-MX USB3, BIOS 0506 08/10/2012
[ 115.807453] task: ffff8804189a0000 ti: ffff8803f74d6000 task.ti: ffff8803f74d6000
--
NULL && (void)
next prev parent reply other threads:[~2013-08-07 21:01 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 [this message]
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
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=87iozhmd0a.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.