From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Yang Z Zhang <yang.z.zhang@intel.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Kevin Tian <kevin.tian@intel.com>
Subject: Re: [PATCH] VT-d: don't crash when PTE bits 52 and up are non-zero
Date: Wed, 7 Jan 2015 10:00:22 -0500 [thread overview]
Message-ID: <20150107150022.GG30457@l.oracle.com> (raw)
In-Reply-To: <54AD155B0200007800052364@mail.emea.novell.com>
On Wed, Jan 07, 2015 at 10:15:39AM +0000, Jan Beulich wrote:
> >>> On 23.12.14 at 07:52, <kevin.tian@intel.com> wrote:
> >> From: Jan Beulich [mailto:JBeulich@suse.com]
> >> Sent: Friday, December 19, 2014 7:26 PM
> >>
> >> This can (and will) be legitimately the case when sharing page tables
> >> with EPT (more of a problem before p2m_access_rwx became zero, but
> >> still possible even now when other than that is the default for a
> >> guest), leading to an unconditional crash (in print_vtd_entries())
> >> when a DMA remapping fault occurs.
> >
> > could you elaborate the scenarios when bits 52+ are non-zero?
> >
> >>
> >> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> >
> > but the changes looks reasonable to me.
> >
> > Signed-off-by: Kevin Tian <kevin.tian@intel.com>
>
> I translated this to a Reviewed-by, as S-o-b doesn't seem to make
> sense here.
>
> Konrad - please indicate whether this can also go into 4.5.
Yes. Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>
> Jan
>
next prev parent reply other threads:[~2015-01-07 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 11:26 [PATCH] VT-d: don't crash when PTE bits 52 and up are non-zero Jan Beulich
2014-12-23 6:52 ` Tian, Kevin
2014-12-23 14:27 ` Jan Beulich
2015-01-07 10:15 ` Jan Beulich
2015-01-07 15:00 ` Konrad Rzeszutek Wilk [this message]
2015-01-08 0:41 ` Tian, Kevin
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=20150107150022.GG30457@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yang.z.zhang@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 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.