From: Arun Sharma <arun.sharma@intel.com>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: [PATCH] shadow-fixes.patch
Date: Sat, 28 May 2005 15:34:07 -0700 [thread overview]
Message-ID: <20050528223407.GA25615@intel.com> (raw)
1. Indexing guest_pt[] can fault. Need to use __copy_from_user. This was
preventing FreeBSD 5.4 and RHEL3 install kernel from booting.
2. Read-only page tables should remain read only on a VMX domain. Linux 2.6
depends on getting a write fault on a L2 page table page.
Signed-off-by: Arun Sharma <arun.sharma@intel.com>
--- 1.114/xen/arch/x86/shadow.c 2005-05-25 03:36:57 -07:00
+++ edited/xen/arch/x86/shadow.c 2005-05-28 15:19:23 -07:00
@@ -1906,7 +1906,7 @@
unsigned long gpfn, unsigned index)
{
unsigned long smfn = __shadow_status(d, gpfn, PGT_snapshot);
- l1_pgentry_t *snapshot; // could be L1s or L2s or ...
+ l1_pgentry_t *snapshot, gpte; // could be L1s or L2s or ...
int entries_match;
perfc_incrc(snapshot_entry_matches_calls);
@@ -1916,10 +1916,14 @@
snapshot = map_domain_mem(smfn << PAGE_SHIFT);
+ if (__copy_from_user(&gpte, &guest_pt[index],
+ sizeof(gpte)))
+ return 0;
+
// This could probably be smarter, but this is sufficent for
// our current needs.
//
- entries_match = !l1e_has_changed(&guest_pt[index], &snapshot[index],
+ entries_match = !l1e_has_changed(&gpte, &snapshot[index],
PAGE_FLAG_MASK);
unmap_domain_mem(snapshot);
@@ -2600,7 +2604,8 @@
if ( unlikely(!(l1e_get_flags(gpte) & _PAGE_RW)) )
{
- if ( shadow_mode_page_writable(d, l1e_get_pfn(gpte)) )
+ if ( shadow_mode_page_writable(d, l1e_get_pfn(gpte))
+ && !shadow_mode_external(d))
{
allow_writes = 1;
l1e_add_flags(&gpte, _PAGE_RW);
next reply other threads:[~2005-05-28 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 22:34 Arun Sharma [this message]
2005-05-29 1:02 ` [PATCH] shadow-fixes.patch Michael A Fetterman
2005-05-30 16:33 ` Arun Sharma
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=20050528223407.GA25615@intel.com \
--to=arun.sharma@intel.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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.