From: Joerg Roedel <joro@8bytes.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
"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 17:39:28 +0200 [thread overview]
Message-ID: <20120927153928.GB18962@8bytes.org> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA908FEF572@SACEXCMBX04-PRD.hq.netapp.com>
On Thu, Sep 27, 2012 at 03:32:02PM +0000, Myklebust, Trond wrote:
> Does your checked out copy of 3.6-rc7 contain commit c50669 (NFS:
> Clear key construction data if the idmap upcall fails)? The latter was
> merged in3.6-rc3, and is reported to fix the problem for the other
> testers.
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.
Joerg
next prev parent reply other threads:[~2012-09-27 15:39 UTC|newest]
Thread overview: 22+ 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: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 [this message]
2012-09-27 16:16 ` Myklebust, Trond
2012-09-27 16:59 ` Linus Torvalds
2012-09-27 21:21 ` Myklebust, Trond
2012-09-27 17:56 ` Joerg Roedel
2012-09-27 18:15 ` Bryan Schumaker
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=20120927153928.GB18962@8bytes.org \
--to=joro@8bytes.org \
--cc=Trond.Myklebust@netapp.com \
--cc=joerg.roedel@amd.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).