From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: Kernel oops in host caused by mmaping RAM Date: Tue, 12 Apr 2011 23:09:01 +0200 Message-ID: <4DA4BF6D.7000607@web.de> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig3D90D4F5A367A7DCA659DEB3" Cc: kvm@vger.kernel.org To: Sasha Levin Return-path: Received: from fmmailgate01.web.de ([217.72.192.221]:40105 "EHLO fmmailgate01.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932155Ab1DLVJD (ORCPT ); Tue, 12 Apr 2011 17:09:03 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3D90D4F5A367A7DCA659DEB3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-04-12 21:41, Sasha Levin wrote: > Hello, >=20 > I've tried using mmap to map the RAM of a guest instead of > posix_memalign which is used both in the kvm tool and qemu. >=20 > Doing so caused a kernel Oops, which happens every time I run the code > and was confirmed both on 2.6.38 and the latest git build of 2.6.39. >=20 Can you share the test case that triggers it? That's easier than guessing what you did precisely. Thanks, Jan --------------enig3D90D4F5A367A7DCA659DEB3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk2kv20ACgkQitSsb3rl5xRHwACfZBGY/X72lH2e2wVZfo6TzjPX oH4AoL3RTt3ZHhCYSE087vT8BSr82WbI =DMlD -----END PGP SIGNATURE----- --------------enig3D90D4F5A367A7DCA659DEB3--