All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [TESTDAY] PV / HVM pass-through works when IOMMU present; weird failures when not
Date: Mon, 01 Jul 2013 13:26:50 +0100	[thread overview]
Message-ID: <51D191AA02000078000E1F24@nat28.tlf.novell.com> (raw)
In-Reply-To: <51D15F9E.4020309@eu.citrix.com>

>>> On 01.07.13 at 12:53, George Dunlap <george.dunlap@eu.citrix.com> wrote:
> On 28/06/13 17:00, Jan Beulich wrote:
>>>>> On 28.06.13 at 17:37, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
>>> - For HVM guests, the only user-visible indication tha the IOMMU has
>>> been disabled is the following error message on the command-line:
>>>
>>> # xl pci-attach h0 07:00.0
>>> libxl: error: libxl_pci.c:949:do_pci_add: xc_assign_device failed
>>>
>>> However, the device itself ends up passed-through to the guest anyway;
>>> the guest seems to be able to see it and interact with it normally.
>>> This is particularly scary, as in theory this should not be possible
>>> without a working IOMMU.
>>>
>>> I don't think this is a blocker for 4.3, but we should definitely
>>> release note it, and for 4.4 add a check to see if there is a
>>> functioning IOMMU and only add a device if there's an override set.
>> To me this very much looks like a security problem (which I
>> think we should fix asap).
> 
> Is it worth delaying the release (yet) another week for?

I would say so, but I'm open to being convinced otherwise.

> Probably the simplest solution at the moment, if there's an easy way for 
> the toolstack to figure out whether there is a working IOMMU or not, is 
> to simply not allow pass-through without an IOMMU unless there is an 
> override option.

xend had no override option - pass-through to HVM without
IOMMU should never be allowed imo.

Adding proper error handling perhaps is indeed beyond what's
reasonable for 4.3, but making use of xc_test_assign_device()
should result in not too big a change.

Jan

      parent reply	other threads:[~2013-07-01 12:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 15:37 [TESTDAY] PV / HVM pass-through works when IOMMU present; weird failures when not George Dunlap
2013-06-28 16:00 ` Jan Beulich
2013-06-28 16:10   ` George Dunlap
2013-07-01 12:14     ` Jan Beulich
2013-06-28 16:13   ` Ian Campbell
2013-07-01 10:53   ` George Dunlap
2013-07-01 12:15     ` George Dunlap
2013-07-01 12:31       ` Jan Beulich
2013-07-01 13:17         ` Ian Jackson
2013-07-01 13:42           ` Jan Beulich
2013-07-01 14:15         ` Stefano Stabellini
2013-07-01 14:19         ` Ian Jackson
2013-07-01 12:26     ` Jan Beulich [this message]

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=51D191AA02000078000E1F24@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.