This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [PATCH, RFC, resend] Re: [Xen-devel] granting access to MSI-X table

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [PATCH, RFC, resend] Re: [Xen-devel] granting access to MSI-X table and pending bit array
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Mon, 16 Aug 2010 08:55:53 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Mon, 16 Aug 2010 00:56:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C88BF72B.1DCAE%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4C6566B2020000780000FBD9@xxxxxxxxxxxxxxxxxx> <C88BF72B.1DCAE%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> On 14.08.10 at 08:32, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> On 13/08/2010 14:37, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
>> Below/attached is an untested and possibly not yet complete patch
>> attempting to address the problem originally described on this thread
>> (can't really test this myself as I don't have, with one exception,
>> any MSI-X capable devices around, and the exceptional one doesn't have
>> a driver making use of it). I had sent it once before, it only got
>> refreshed since then to build with xen-unstable as of c/s 21952, and
>> I'm re-sending it mainly because there was no feedback so far, despite
>> the original problem representing a security issue.
> I'm happy to check it in and see if anyone complains about breakage.

It's not really only a matter of doing a trial checkin, but also one of
finding a solution to the remaining pv-guest issue described in the
submission mail as well as the removal the remaining hole left due to
qemu temporarily mapping this space read/write for no apparent
reason other than keeping the code simple.


Xen-devel mailing list