From: Bryan Schumaker <bjschuma@netapp.com>
To: Frank Nicholas <frank@nicholasfamilycentral.com>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
Jim Rees <rees@umich.edu>,
"Schumaker, Bryan" <Bryan.Schumaker@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"bfields@fieldses.org" <bfields@fieldses.org>
Subject: Re: kernel BUG at fs/nfs/idmap.c:684!
Date: Tue, 28 Aug 2012 16:05:35 -0400 [thread overview]
Message-ID: <503D248F.5040900@netapp.com> (raw)
In-Reply-To: <B3C42AF5-88C8-4AF7-9B2C-C0510A73BDB1@nicholasfamilycentral.com>
On 08/28/2012 03:55 PM, Frank Nicholas wrote:
> On Aug 28, 2012, at 2:47 PM, Frank Nicholas <frank@nicholasfamilycentral.com> wrote:
>
>> On Aug 28, 2012, at 2:08 PM, Bryan Schumaker <bjschuma@netapp.com> wrote:
>>
>>> On 08/28/2012 02:06 PM, Myklebust, Trond wrote:
>>>> On Tue, 2012-08-28 at 14:01 -0400, Frank Nicholas wrote:
>>>>
>>>> An early version of those patches did indeed cause problems such as the
>>>> above. Are you sure that you applied the patches that actually went
>>>> upstream in
>>>
>>> No, I don't think he did. I forgot you fixed up a few things, so I sent him the last copy I had.
>>>
>>> - Bryan
>>>
>>>>
>>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=c5066945b7ea346a11424dbeb7830b7d7d00c206
>>>> and
>>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=12dfd080556124088ed61a292184947711b46cbe
>>>>
>>>
>>
>>
>> rpc.idmapd is running.
>>
>> I applied the patches Bryan e-mailed me. I'll apply the linked patches & confirm they clear up the log entries.
>>
>> Thanks.
>
> Linked patches have been applied. syslog messages are gone and all seems to be good.
>
> What version of the kernel will include these patches?
I think 3.5.4, Greg K-H sent out email yesterday saying that they had just been added to the stable tree.
- Bryan
>
> Thanks everyone for the quick replies & solution!
>
prev parent reply other threads:[~2012-08-28 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 12:42 kernel BUG at fs/nfs/idmap.c:684! Frank Nicholas
2012-08-28 12:49 ` Frank Nicholas
2012-08-28 14:43 ` Bryan Schumaker
2012-08-28 17:05 ` Frank Nicholas
2012-08-28 17:43 ` Jim Rees
2012-08-28 17:46 ` Frank Nicholas
2012-08-28 18:01 ` Frank Nicholas
2012-08-28 18:05 ` Bryan Schumaker
2012-08-28 18:06 ` Myklebust, Trond
2012-08-28 18:08 ` Bryan Schumaker
2012-08-28 18:47 ` Frank Nicholas
2012-08-28 19:55 ` Frank Nicholas
2012-08-28 20:05 ` Bryan Schumaker [this message]
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=503D248F.5040900@netapp.com \
--to=bjschuma@netapp.com \
--cc=Bryan.Schumaker@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=frank@nicholasfamilycentral.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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.