virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Chris Malley <mail@chrismalley.co.uk>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: lguest@ozlabs.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/5] Boot protocol changes
Date: Thu, 04 Oct 2007 12:20:54 +0100	[thread overview]
Message-ID: <1191496854.7083.5.camel@feisty> (raw)
In-Reply-To: <1191494843.8268.157.camel@localhost.localdomain>

On Thu, 2007-10-04 at 20:47 +1000, Rusty Russell wrote:
> On Thu, 2007-10-04 at 10:47 +0100, Chris Malley wrote:
> > Hi guys
> > 
> > I gave these patches a try (on top of 2.6.23-rc9 plus the previously
> > submitted 2.6.24 patch set).
> > 
> > The last two seem to cause Badness on my system, whereby if I start a
> > guest (using the same bzImage as the host, as before) it seems to boot
> > OK, and the host system still superficially looks stable (my X session
> > is OK and I can interact with existing processes) but if I attempt to
> > launch any new process on the host (even typing "ls" into a terminal
> > window) I get a Segmentation fault.
> 
> I think this might actually be caused by a nasty bug in one of the
> previous patches (patch 27).  I found it because every second time I
> launched a guest it failed.  Strange, huh?
> 
> These lines in drivers/lguest/page_tables.c:
> 
> +               pte_t ro_gpte = gpte;
> +               pte_wrprotect(ro_gpte);
> 
> Should be:
> 
> +               pte_t ro_gpte = pte_wrprotct(gpte);
just being pedantic I assume you mean:
  +               pte_t ro_gpte = pte_wrprotect(gpte);

> That's the only "break the host" issue I know of...
> 
> Thanks!
> Rusty.

Yep, that fixes it, thanks Rusty!

--
Chris

      reply	other threads:[~2007-10-04 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04  9:47 [PATCH 0/5] Boot protocol changes Chris Malley
2007-10-04 10:47 ` Rusty Russell
2007-10-04 11:20   ` Chris Malley [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=1191496854.7083.5.camel@feisty \
    --to=mail@chrismalley.co.uk \
    --cc=lguest@ozlabs.org \
    --cc=rusty@rustcorp.com.au \
    --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;
as well as URLs for NNTP newsgroup(s).