From: Bryan Schumaker <bjschuma@netapp.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
Joerg Roedel <joro@8bytes.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Subject: Re: kernel BUG at /data/lemmy/linux.trees.git/fs/nfs/idmap.c:681!
Date: Thu, 27 Sep 2012 14:15:21 -0400 [thread overview]
Message-ID: <506497B9.3030601@netapp.com> (raw)
In-Reply-To: <20120927175623.GG10549@amd.com>
On 09/27/2012 01:56 PM, Joerg Roedel wrote:
> On Thu, Sep 27, 2012 at 04:16:25PM +0000, Myklebust, Trond wrote:
>>> Yes, it contains that commit. I was about to test plain v3.6-rc7 without
>>> my patches (not nfs related, of cource) on-top, but unfortunatly the
>>> disk with the root-fs died :-/
>>> I am about to set up the box again and test plain -rc7.
>>
>> Please do.
>
> Okay, the box is running again and the bug does not reproduce anymore
> with the new installation. Unfortunatly the old kernel configuration is
> gone together with the previous version of the nfs-utils :-/ I'll try to
> play around with the kernel config a little bit more and see if it
> reproduces again.
Double check that you're using the legacy idmapper, and not the keyring based one (/etc/request-key.conf shouldn't have the "create id_resolver * * /usr/bin/nfsidmap %k %d" line).
- Bryan
>
>
> Joerg
>
next prev parent reply other threads:[~2012-09-27 18:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 13:41 kernel BUG at /data/lemmy/linux.trees.git/fs/nfs/idmap.c:681! Joerg Roedel
2012-08-07 13:55 ` Bryan Schumaker
2012-08-07 14:15 ` Joerg Roedel
2012-08-07 14:17 ` Bryan Schumaker
2012-08-07 14:27 ` Joerg Roedel
2012-08-07 14:36 ` Bryan Schumaker
2012-08-07 14:50 ` Joerg Roedel
2012-08-07 15:12 ` Bryan Schumaker
2012-08-07 15:19 ` Myklebust, Trond
2012-08-07 15:19 ` Myklebust, Trond
2012-08-07 15:14 ` Myklebust, Trond
2012-08-07 15:14 ` Myklebust, Trond
2012-08-07 15:18 ` Bryan Schumaker
2012-09-27 14:52 ` Joerg Roedel
2012-09-27 15:32 ` Myklebust, Trond
2012-09-27 15:39 ` Joerg Roedel
2012-09-27 16:16 ` Myklebust, Trond
2012-09-27 16:16 ` Myklebust, Trond
2012-09-27 16:59 ` Linus Torvalds
2012-09-27 17:30 ` BUG_ON/panic proliferation Dave Jones
2012-09-28 0:52 ` Ryan Mallon
2012-09-28 10:08 ` Alan Cox
2012-09-27 21:21 ` kernel BUG at /data/lemmy/linux.trees.git/fs/nfs/idmap.c:681! Myklebust, Trond
2012-09-27 21:21 ` Myklebust, Trond
2012-09-27 17:56 ` Joerg Roedel
2012-09-27 18:15 ` Bryan Schumaker [this message]
2012-09-28 12:17 ` Joerg Roedel
2012-09-28 13:21 ` Bryan Schumaker
2012-09-28 13:34 ` Joerg Roedel
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=506497B9.3030601@netapp.com \
--to=bjschuma@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.