From: Al Viro <viro@ZenIV.linux.org.uk>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [process_vm_access] BUG: unable to handle kernel paging request at fffffff27b92dd20
Date: Mon, 10 Feb 2014 20:04:36 +0000 [thread overview]
Message-ID: <20140210200436.GE18016@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20140210112231.GA11951@localhost>
On Mon, Feb 10, 2014 at 07:22:31PM +0800, Fengguang Wu wrote:
> Hi Al,
>
> 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.
Actually, that's a combination of 3 bugs, only one of them being in this
commit. See current #iov_iter; AFAICS, all process_vm stuff in LTP passes
with it.
BTW, what's the story with ioctl3? What I'm getting from it is
"Must supply a file collection or a command", with no further
explanations. Something it wants installed that just isn't there?
next prev parent reply other threads:[~2014-02-10 20:04 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 [this message]
2014-02-12 0:27 ` Andrew Morton
2014-02-12 0:38 ` Al Viro
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=20140210200436.GE18016@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--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.