From: "Richard W.M. Jones" <rjones@redhat.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: kvm [2087]: load/store instruction decoding not implemented
Date: Tue, 24 Feb 2015 14:36:08 +0000 [thread overview]
Message-ID: <20150224143608.GO11603@redhat.com> (raw)
In-Reply-To: <54EC8654.1060905@arm.com>
On Tue, Feb 24, 2015 at 02:10:28PM +0000, Marc Zyngier wrote:
> On 24/02/15 13:45, Richard W.M. Jones wrote:
> > On Tue, Feb 24, 2015 at 01:12:49PM +0000, Marc Zyngier wrote:
> >> Here's my theory: userspace is accessing something it should never
> >> access (outside of RAM, basically), and doing so via a kernel interface.
> >>
> >> Is this process accessing /dev/mem by any chance? dmidecode anyone?
> >
> > Not as far as I know. The userspace process is inserting modules.
> >
> > Here is the userspace function which is most likely to be running:
> >
> > https://github.com/libguestfs/supermin/blob/master/src/init.c#L292
>
> Hmmm. That seems quite inoffensive indeed...
>
> > Unfortunately because of lack of a full stack trace, I can't be sure
> > exactly what system call is failing, but I'll probably add more debug
> > to the userspace program later.
> >
> > BTW this worked fine in 3.19. It's started failing in 3.20/4.0. It
> > also works fine on x86.
>
> Any chance you could find out whether that's a host or guest regression?
Here is a summary of the test combinations that I have run:
guest kernel host kernel result
--------------------------------------------------------
3.19.0-0.rc7 3.19.0-0.rc7 no bug seen
3.20.0-0.rc0 3.19.0-0.rc7 bug seen
3.19.0-0.rc7 4.0.0-0.rc1 no bug seen
4.0.0-0.rc1 4.0.0-0.rc1 bug seen
So a guest regression, I think?
It's also possible the bug existed in old kernels but was masked
somehow, eg. different memory layout.
I can probably bisect this given time, but I'm going to try putting
some debug into the userspace process to find out which system call
fails first.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
next prev parent reply other threads:[~2015-02-24 14:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 11:59 kvm [2087]: load/store instruction decoding not implemented Richard W.M. Jones
2015-02-24 12:15 ` Peter Maydell
2015-02-24 12:29 ` Richard W.M. Jones
2015-02-24 12:47 ` Christoffer Dall
2015-02-24 13:12 ` Marc Zyngier
2015-02-24 13:45 ` Richard W.M. Jones
2015-02-24 14:10 ` Marc Zyngier
2015-02-24 14:36 ` Richard W.M. Jones [this message]
2015-02-24 14:42 ` Marc Zyngier
2015-02-24 14:43 ` Richard W.M. Jones
2015-02-24 15:03 ` Marc Zyngier
2015-02-24 15:09 ` Richard W.M. Jones
2015-02-24 15:20 ` Marc Zyngier
2015-02-24 16:37 ` Marc Zyngier
2015-02-24 14:25 ` Richard W.M. Jones
2015-02-24 14:55 ` Christoffer Dall
2015-02-24 15:06 ` Peter Maydell
2015-02-24 15:22 ` Richard W.M. Jones
2015-02-24 12:57 ` Peter Maydell
2015-02-24 12:16 ` Christoffer Dall
2015-02-24 12:27 ` Richard W.M. Jones
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=20150224143608.GO11603@redhat.com \
--to=rjones@redhat.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
/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