All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
	Tim Deegan <Tim.Deegan@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH]Add a flag for shadow pages
Date: Wed, 04 Mar 2009 09:56:29 +0000	[thread overview]
Message-ID: <C5D400CD.4168%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098401C7C9DD9D@PDSMSX501.ccr.corp.intel.com>

On 04/03/2009 09:28, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:

> Keir Fraser <mailto:keir.fraser@eu.citrix.com> wrote:
>> I just realised that. You use get_page() to lock down a page's owner.
>> Otherwise it can change under your feet anyway. You don't need
> 
> With get_page_owner() in get_page() will cause fault if it is a shadow page.
> Or you mean use exception table to protect it?

There are a few solutions. One would be to remove the debug printk from
get_page() since it is the only thing which dereferences the bogus 'domain
pointer'.

Another would be to create a new function page_get_reference_and_owner()
which obtains a reference on a guest page and *returns* the (now known
valid) domain pointer. Probably this is nicer actually. Then all existing
users of page_get_owner() need checking to ensure they don't need to use the
new more expensive function -- I think some are probably actually unsafe now
that shadow pages clobber the domain field.

 -- Keir

  reply	other threads:[~2009-03-04  9:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04  8:46 [PATCH]Add a flag for shadow pages Jiang, Yunhong
2009-03-04  9:06 ` Keir Fraser
2009-03-04  9:17   ` Jiang, Yunhong
2009-03-04  9:22     ` Keir Fraser
2009-03-04  9:28       ` Jiang, Yunhong
2009-03-04  9:56         ` Keir Fraser [this message]
2009-03-04 11:57           ` Keir Fraser
2009-03-04 12:13             ` Tim Deegan
2009-03-04 13:19               ` Keir Fraser
2009-03-04 14:30             ` Keir Fraser
2009-03-04 16:01               ` Jiang, Yunhong
2009-03-04 16:32                 ` Gianluca Guida
2009-03-05  2:41                   ` Jiang, Yunhong
2009-03-04 16:45                 ` Keir Fraser
2009-03-04  9:20 ` Keir Fraser

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=C5D400CD.4168%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Tim.Deegan@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@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.