From: Alex Williamson <alex.williamson@redhat.com>
To: Avi Kivity <avi@redhat.com>, chrisw <chrisw@sous-sol.org>
Cc: "Hao, Xudong" <xudong.hao@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM Test report, kernel a685b38... qemu 671d89d...
Date: Wed, 16 Feb 2011 08:01:11 -0700 [thread overview]
Message-ID: <1297868471.14733.186.camel@x201> (raw)
In-Reply-To: <4D5B9487.2030309@redhat.com>
On Wed, 2011-02-16 at 11:10 +0200, Avi Kivity wrote:
> On 02/16/2011 11:05 AM, Hao, Xudong wrote:
> > Hi, all,
> > This is KVM test result against kvm.git a685b38e272587e644fedd37269ddb82df21c052, and qemu-kvm.git 671d89d6411655bb4f8058ce6eb86bb0bb8ec978.
> >
> > Currently qemu-kvm can build successfully on RHEL5, and Qcow image create failure issue also got fixed, our nightly testing resumed. One VT-d device assignment issue opened on latest KVM.
> >
> > New issue:
> > 1. [VT-d] VT-d device passthrough fail to guest
> > https://bugzilla.kernel.org/show_bug.cgi?id=29232
> >
Extremely reproducible. Looks like it's a result of this kernel change:
commit 47970b1b2aa64464bc0a9543e86361a622ae7c03
Author: Chris Wright <chrisw@sous-sol.org>
Date: Thu Feb 10 15:58:56 2011 -0800
pci: use security_capable() when checking capablities during config space re
Eric Paris noted that commit de139a3 ("pci: check caps from sysfs file
open to read device dependent config space") caused the capability check
to bypass security modules and potentially auditing. Rectify this by
calling security_capable() when checking the open file's capabilities
for config space reads.
Reported-by: Eric Paris <eparis@redhat.com>
Signed-off-by: Chris Wright <chrisw@sous-sol.org>
Signed-off-by: James Morris <jmorris@namei.org>
Chris, why isn't this working for us? Thanks,
Alex
next prev parent reply other threads:[~2011-02-16 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 9:05 KVM Test report, kernel a685b38... qemu 671d89d Hao, Xudong
2011-02-16 9:10 ` Avi Kivity
2011-02-16 15:01 ` Alex Williamson [this message]
2011-02-16 15:06 ` Alex Williamson
2011-02-16 15:16 ` Chris Wright
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=1297868471.14733.186.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=kvm@vger.kernel.org \
--cc=xudong.hao@intel.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