From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [process_vm_access] BUG: unable to handle kernel paging request at fffffff27b92dd20
Date: Wed, 12 Feb 2014 00:38:03 +0000 [thread overview]
Message-ID: <20140212003803.GL18016@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20140211162745.c4fdb96ec58fa9581e6c2841@linux-foundation.org>
On Tue, Feb 11, 2014 at 04:27:45PM -0800, Andrew Morton wrote:
> On Mon, 10 Feb 2014 19:22:31 +0800 Fengguang Wu <fengguang.wu@intel.com> wrote:
>
> > We noticed the below oops since commit 68a25f08c9bec07ad95e55a01b127168e43aed84
> > ("process_vm_access: take get_user_pages/put_pages one level up")
> > while running ltp tests inside kvm.
>
> I can't find this patch anywhere. Where did it come from?
It used to be in vfs.git#iov_iter; fixed since then, but this stuff is still
not in #for-next.
prev parent reply other threads:[~2014-02-12 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 11:22 [process_vm_access] BUG: unable to handle kernel paging request at fffffff27b92dd20 Fengguang Wu
2014-02-10 11:25 ` Fengguang Wu
2014-02-10 20:04 ` Al Viro
2014-02-12 0:27 ` Andrew Morton
2014-02-12 0:38 ` Al Viro [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=20140212003803.GL18016@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@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.