From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCH, RFC, resend] Re: granting access to MSI-X table and pending bit array Date: Mon, 16 Aug 2010 08:55:53 +0100 Message-ID: <4C690B29020000780000FF93@vpn.id2.novell.com> References: <4C6566B2020000780000FBD9@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "xen-devel@lists.xensource.com" , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org >>> On 14.08.10 at 08:32, Keir Fraser wrote: > On 13/08/2010 14:37, "Jan Beulich" wrote: >=20 >> 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. >=20 > 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. Jan