From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 103141] Host-triggerable NULL pointer oops
Date: Mon, 24 Aug 2015 15:46:12 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path:
Received: from mail.kernel.org ([198.145.29.136]:47192 "EHLO mail.kernel.org"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S1754610AbbHXPqR (ORCPT );
Mon, 24 Aug 2015 11:46:17 -0400
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 01C8B20790
for ; Mon, 24 Aug 2015 15:46:15 +0000 (UTC)
Received: from bugzilla2.web.kernel.org (bugzilla2.web.kernel.org [172.20.200.52])
by mail.kernel.org (Postfix) with ESMTP id 59C9620785
for ; Mon, 24 Aug 2015 15:46:13 +0000 (UTC)
In-Reply-To:
Sender: kvm-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=103141
--- Comment #2 from felix ---
Created attachment 185681
--> https://bugzilla.kernel.org/attachment.cgi?id=185681&action=edit
Test program 2 (C99)
You mean "can" as in "I think it does" or "it did for me"?
And anyway, it seems to only fix the most proximate cause of the crash. My
biggest worry is that KVM_SET_USER_MEMORY_REGION ioctls with guest_phys_addr
around the 0xfff00000 to 0xffff0000 range seem not to "register"; starting the
VM looks like as if the region wasn't placed there.
I attach test program 2. Running that on my system with 0x44000 as an argument
outputs "halted" (as expected), but 0x45000 and larger multiples of 0x1000 give
"internal error, subcode 1".
--
You are receiving this mail because:
You are watching the assignee of the bug.