linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Dauchy <wdauchy@gmail.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "Schumaker, Bryan" <Bryan.Schumaker@netapp.com>,
	Linux NFS mailing list <linux-nfs@vger.kernel.org>,
	David Howells <dhowells@redhat.com>
Subject: Re: wait_for_key_construction oops
Date: Thu, 2 Aug 2012 23:54:10 +0200	[thread overview]
Message-ID: <CAJ75kXbmo4FQwpFVk2NC9y5+jXpaEvUVr_viiTRMtA6mn28oVA@mail.gmail.com> (raw)
In-Reply-To: <1343943192.26497.2.camel@lade.trondhjem.org>

Hi Trond,

Thank you for your reply.

On Thu, Aug 2, 2012 at 11:33 PM, Myklebust, Trond
<Trond.Myklebust@netapp.com> wrote:
> Have you applied commit b1027439dff844675f6c0df97a1b1d190791a699 (NFS:
> Force the legacy idmapper to be single threaded)? That patch is Cc:
> stable [>=3.4], and so needs to be applied to your kernel.
> There is also a minor fix from Dan Carpenter in commit
> 5abc03cd919535c61b813f2319cb38326a41e810 (NFS: kmalloc() doesn't return
> an ERR_PTR()) that should be applied.

Yes I have these two patches applied. I got the same trace with a
3.4.7 kernel including these patches.

-- 
William

  reply	other threads:[~2012-08-02 21:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJ75kXZb2_MGOrxG6JRyGEKdHm+t_yUk755DpqTvpdyVZ4TFzg@mail.gmail.com>
2012-07-30 22:28 ` wait_for_key_construction oops Myklebust, Trond
2012-07-31  8:07   ` William Dauchy
2012-08-02 21:28     ` William Dauchy
2012-08-02 21:33       ` Myklebust, Trond
2012-08-02 21:54         ` William Dauchy [this message]
2012-09-20 14:27 William Dauchy
2012-09-20 16:11 ` Myklebust, Trond

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=CAJ75kXbmo4FQwpFVk2NC9y5+jXpaEvUVr_viiTRMtA6mn28oVA@mail.gmail.com \
    --to=wdauchy@gmail.com \
    --cc=Bryan.Schumaker@netapp.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=dhowells@redhat.com \
    --cc=linux-nfs@vger.kernel.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).