From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@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, 1 Jul 2013 14:17:58 +0100 [thread overview]
Message-ID: <20945.33158.647741.589514@mariner.uk.xensource.com> (raw)
In-Reply-To: <51D192DA02000078000E1F38@nat28.tlf.novell.com>
Jan Beulich writes ("Re: [Xen-devel] [TESTDAY] PV / HVM pass-through works when IOMMU present; weird failures when not"):
> As per the above and the earlier reply I sent, I don't think we
> should release without this fixed. Let me see whether the minimal
> fix I sketched out earlier works...
As I just wrote on IRC (Jan, you seem to have fallen off the channel);
14:08 <Diziet> Re Jan's comments. To be clear, this isn't a regression
compared to 4.2, right ?
14:10 <Diziet> I think the right answer is to treat this as an embargo-less
security problem. Preparing a proper security patch for that
probably involves fixing the error handling.
14:10 <Diziet> And that might take a week.
14:10 <Diziet> I'm really not keen on this "extra check" approach.
14:11 <Diziet> So I would go ahead with the release tomorrow.
next prev parent reply other threads:[~2013-07-01 13:17 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 [this message]
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
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=20945.33158.647741.589514@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.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.