From: Mark McLoughlin <markmc@redhat.com>
To: jeremy@goop.org
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
xen-devel@lists.xensource.com,
Mark McLoughlin <markmc@redhat.com>
Subject: [PATCH 3/3] xen: Clear PG_pinned in release_{pte,pmd}()
Date: Fri, 28 Mar 2008 16:38:17 +0000 [thread overview]
Message-ID: <1206722297-11763-4-git-send-email-markmc@redhat.com> (raw)
In-Reply-To: <1206722297-11763-3-git-send-email-markmc@redhat.com>
We don't currently clear PG_pinned in release_pt(),
probably because the page is to be freed anyway,
but it jumps out as an obvious gap in the logic
so add clear the flag for consistency sake.
Signed-off-by: Mark McLoughlin <markmc@redhat.com>
---
arch/x86/xen/enlighten.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
index 0ce225f..8c5ff24 100644
--- a/arch/x86/xen/enlighten.c
+++ b/arch/x86/xen/enlighten.c
@@ -719,6 +719,7 @@ static void xen_release_ptpage(u32 pfn, unsigned level)
pin_pagetable_pfn(MMUEXT_UNPIN_TABLE, pfn);
make_lowmem_page_readwrite(__va(PFN_PHYS(pfn)));
}
+ ClearPagePinned(page);
}
}
--
1.5.4.1
next prev parent reply other threads:[~2008-03-28 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 16:38 [PATCH 0/3] xen: Fix oops when mapping/unmapping addr above 1Gb Mark McLoughlin
2008-03-28 16:38 ` [PATCH 1/3] xen: Refactor xen_{alloc,release}_{pte,pmd}() Mark McLoughlin
2008-03-28 16:38 ` [PATCH 2/3] xen: Do not pin/unpin PMD pages Mark McLoughlin
2008-03-28 16:38 ` Mark McLoughlin [this message]
2008-03-28 18:02 ` [PATCH 0/3] xen: Fix oops when mapping/unmapping addr above 1Gb Jeremy Fitzhardinge
2008-03-31 13:14 ` Ingo Molnar
2008-03-31 14:55 ` Jeremy Fitzhardinge
2008-04-02 14:35 ` Mark McLoughlin
2008-04-02 14:36 ` [PATCH 1/3] xen: Refactor xen_{alloc,release}_{pt,pd}() Mark McLoughlin
2008-04-02 14:36 ` [PATCH 2/3] xen: Do not pin/unpin PMD pages Mark McLoughlin
2008-04-02 14:36 ` [PATCH 3/3] xen: Clear PG_pinned in release_{pt,pd}() Mark McLoughlin
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=1206722297-11763-4-git-send-email-markmc@redhat.com \
--to=markmc@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox