From: Rusty Russell <rusty@rustcorp.com.au>
To: Zachary Amsden <zach@vmware.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
lguest <lguest@ozlabs.org>,
Andrew Morton <akpm@linux-foundation.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Lguest] [PATCH] lguest: Fix Malicious Guest GDT Host Crash
Date: Fri, 10 Aug 2007 22:04:00 +1000 [thread overview]
Message-ID: <1186747440.23993.34.camel@localhost.localdomain> (raw)
In-Reply-To: <46BB3692.5010003@vmware.com>
On Thu, 2007-08-09 at 08:45 -0700, Zachary Amsden wrote:
> Rusty Russell wrote:
> > We kill the Guest if it causes a fault in the Switcher: it's the
> > Guest's responsibility to make sure it's not using segments when it
> > changes them.
>
> Linux doesn't obey that rule. It changes descriptors behind FS/GS all
> over the place. Well, not all over the place, only when updating LDT
> entries
Hi Zach,
I think it's OK. To clarify, it's only fatal when the guest changes
them in a way that will fault if they're reloaded: not any change.
Lguest doesn't support LDT, so that's not a problem.
> , TLS entries, and during context switch.
These two go through load_TLS -> lguest_load_tls which is patched by
this same change to load 0 into gs before doing the hypercall. The
other segment registers are set by the kernel, and so we know they don't
refer to changing entries.
Is there anything I've missed?
Rusty.
prev parent reply other threads:[~2007-08-10 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 10:57 [PATCH] lguest: Fix Malicious Guest GDT Host Crash Rusty Russell
2007-08-09 15:45 ` [Lguest] " Zachary Amsden
2007-08-10 12:04 ` 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=1186747440.23993.34.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zach@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox