From: Marcelo Tosatti <mtosatti@redhat.com>
To: Rom Freiman <rom@stratoscale.com>
Cc: Muli Ben-Yehuda <mulix@mulix.org>,
kvm@vger.kernel.org, pbonzini@redhat.com,
xiaoguangrong@linux.vnet.ibm.com,
Benoit Hudzia <benoit@stratoscale.com>,
Abel Gordon <abel@stratoscale.com>,
Dan Aloni <alonid@stratoscale.com>
Subject: Re: KVM: MMU: handle invalid root_hpa at __direct_map
Date: Sun, 22 Dec 2013 12:56:49 -0200 [thread overview]
Message-ID: <20131222145649.GA6611@amt.cnet> (raw)
In-Reply-To: <CADs-y4TpXQ0zvg4p-_fkKkMDbEiho89hzhkSAYMEVAxbp63XzQ@mail.gmail.com>
On Sun, Dec 22, 2013 at 11:17:21AM +0200, Rom Freiman wrote:
> Hello everyone,
>
> I've been chasing this bug for a while.
>
> According to my research, this bug fix is works fine for
> 3.11.9-200.fc19.x86_64 kernel version (and I also came to almost similar
> solution and really solved the crash).
>
> But, the problem is, that it seems that this patch does not work on 3.13.0-rc2+
> - it looks like the code flow is different and it crashes in ept_page_fault
> and does not reach __direct_map:
Yep, similar problem, care to send a patch against
FNAME(page_fault), kvm_mmu_get_spte_hierarchy
Maybe there are more vulnerable sites, should secure them all.
next parent reply other threads:[~2013-12-22 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADs-y4TpXQ0zvg4p-_fkKkMDbEiho89hzhkSAYMEVAxbp63XzQ@mail.gmail.com>
2013-12-22 14:56 ` Marcelo Tosatti [this message]
2013-12-27 19:43 ` KVM: MMU: handle invalid root_hpa at __direct_map Marcelo Tosatti
2014-01-16 23:17 ` Rom Freiman
2014-01-17 21:39 ` Marcelo Tosatti
2013-12-19 17:28 Marcelo Tosatti
2013-12-20 9:15 ` Xiao Guangrong
2013-12-20 12:59 ` Marcelo Tosatti
2013-12-20 18:22 ` Paolo Bonzini
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=20131222145649.GA6611@amt.cnet \
--to=mtosatti@redhat.com \
--cc=abel@stratoscale.com \
--cc=alonid@stratoscale.com \
--cc=benoit@stratoscale.com \
--cc=kvm@vger.kernel.org \
--cc=mulix@mulix.org \
--cc=pbonzini@redhat.com \
--cc=rom@stratoscale.com \
--cc=xiaoguangrong@linux.vnet.ibm.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.