From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH, RFC, resend] Re: granting access to MSI-X table and pending bit array
Date: Sat, 14 Aug 2010 07:32:59 +0100 [thread overview]
Message-ID: <C88BF72B.1DCAE%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C6566B2020000780000FBD9@vpn.id2.novell.com>
On 13/08/2010 14:37, "Jan Beulich" <JBeulich@novell.com> 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.
-- Keir
next prev parent reply other threads:[~2010-08-14 6:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 13:37 [PATCH, RFC, resend] Re: granting access to MSI-X table and pending bit array Jan Beulich
2010-08-14 6:32 ` Keir Fraser [this message]
2010-08-16 7:55 ` Jan Beulich
2010-08-26 6:24 ` Jiang, Yunhong
2010-08-26 7:06 ` Jan Beulich
2010-08-26 8:41 ` Jiang, Yunhong
2010-08-26 11:22 ` Jan Beulich
2010-08-27 1:48 ` Jiang, Yunhong
2010-08-27 9:10 ` Jan Beulich
2010-08-27 9:38 ` Jiang, Yunhong
2010-09-01 7:39 ` Jiang, Yunhong
2010-09-15 1:32 ` Jiang, Yunhong
2010-09-15 6:52 ` Keir Fraser
2010-09-15 7:02 ` Jiang, Yunhong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C88BF72B.1DCAE%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).