From: Andre Tomt <andre@tomt.net>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"Schumaker, Bryan" <Bryan.Schumaker@netapp.com>,
Linux-NFS <linux-nfs@vger.kernel.org>,
Fengguang Wu <fengguang.wu@intel.com>,
David Howells <dhowells@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: BUG in __key_instantiate_and_link(): unable to handle kernel paging request at 0000632e6472616f
Date: Tue, 26 Jun 2012 09:24:09 +0200 [thread overview]
Message-ID: <4FE96399.8040608@tomt.net> (raw)
In-Reply-To: <4FE215FE.6010406@netapp.com>
On 20. juni 2012 20:27, Bryan Schumaker wrote:
> Hi Andre,
>
> Have you had a chance to test my patch (below) yet?
I reverted from using keyutils yesterday, verified the problem had
returned, then patched the same kernel with just this patch - so far its
been running fine for 15 hours. Without the patch it would fall over
within 1-2 hours.
So thumbs up from me
Sorry about the delay, once I got it working with keyutils I suddenly
got very, very lazy ;-)
next prev parent reply other threads:[~2012-06-26 7:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 3:41 BUG in __key_instantiate_and_link(): unable to handle kernel paging request at 0000632e6472616f Fengguang Wu
2012-06-01 9:31 ` ethan zhao
2012-06-01 13:50 ` David Howells
2012-06-01 14:24 ` David Howells
2012-06-01 14:34 ` Fengguang Wu
2012-06-02 2:25 ` ethan zhao
2012-06-02 2:25 ` ethan zhao
2012-06-16 2:32 ` Andre Tomt
2012-06-16 18:43 ` Andre Tomt
2012-06-16 19:59 ` Myklebust, Trond
2012-06-16 19:59 ` Myklebust, Trond
2012-06-18 9:04 ` Andre Tomt
2012-06-18 13:28 ` Myklebust, Trond
2012-06-18 13:28 ` Myklebust, Trond
2012-06-18 16:11 ` Bryan Schumaker
2012-06-20 18:27 ` Bryan Schumaker
2012-06-26 7:24 ` Andre Tomt [this message]
2012-06-26 12:42 ` Bryan Schumaker
2012-06-18 12:44 ` Bryan Schumaker
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=4FE96399.8040608@tomt.net \
--to=andre@tomt.net \
--cc=Bryan.Schumaker@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bjschuma@netapp.com \
--cc=dhowells@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.