Linux virtualization list
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: ron minnich <rminnich@gmail.com>
Cc: lguest <lguest@ozlabs.org>,
	virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] Fix Malicious Guest GDT Host Crash
Date: Thu, 09 Aug 2007 15:13:50 +1000	[thread overview]
Message-ID: <1186636430.17752.35.camel@localhost.localdomain> (raw)
In-Reply-To: <13426df10708082140r61dbaf0m7f03da23e8bf0421@mail.gmail.com>

On Wed, 2007-08-08 at 21:40 -0700, ron minnich wrote:
> On 8/7/07, Rusty Russell <rusty@rustcorp.com.au> wrote:
> > Hi all,
> >
> >         Testing would be appreciated (esp. Ron?): I'd like to push this as soon
> > as possible into 2.6.23.  I thought of it while pondering kvm-lite, and
> > then proved it was a problem...
> 
> Works fine here.
> 
> Be aware that in the early Plan 9 port to lguest I created a gdt entry
> and forgot to wrap the GDT #  with a macro with the result that I
> loaded a gdt # instead of a selector into the gdt entry, and when the
> guest switched back to the host (and back to guest, I guess) it
> crashed my machine so hard that it went into the BIOS 'let's set this
> brand new thinkpad up' dialog.

Wow.  That's impressive.  It's understandable, however: I got a host
triplefault here when a malformed GDT entry caused a #GP on guest entry.

I'd be interested to check that this fixes it, but I'm pretty confident
(it fixed it here).

> The guys at the Plan 9  BOF at Google thought lguest was pretty darn cool.

Cool!

Rusty.

      reply	other threads:[~2007-08-09  5:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08  4:10 [PATCH] Fix Malicious Guest GDT Host Crash Rusty Russell
2007-08-09  4:40 ` ron minnich
2007-08-09  5:13   ` Rusty Russell [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=1186636430.17752.35.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=lguest@ozlabs.org \
    --cc=rminnich@gmail.com \
    --cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox