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 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. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ _______________________________________________ kvmarm mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
