From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Fix swap and page migration for LPAE
Date: Thu, 26 Jul 2012 17:01:06 +0100 [thread overview]
Message-ID: <1343318468-10412-1-git-send-email-will.deacon@arm.com> (raw)
Hello,
These two patches fix swapping and page migration for LPAE-enabled
kernels. Without these changes, we corrupt the offset stored in the file
pte when updating the page tables and may truncate the pfn when storing
it into a swp_entry_t.
I'll CC stable on the final patches.
All feedback welcome,
Will
Will Deacon (2):
ARM: mm: avoid setting nG bit for user mappings that aren't present
ARM: mm: use 5 bits for swapfile type encoding
arch/arm/include/asm/pgtable.h | 40 +++++++++++++++++++++-------------------
arch/arm/mm/flush.c | 2 --
2 files changed, 21 insertions(+), 21 deletions(-)
--
1.7.4.1
next reply other threads:[~2012-07-26 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 16:01 Will Deacon [this message]
2012-07-26 16:01 ` [PATCH 1/2] ARM: mm: avoid setting nG bit for user mappings that aren't present Will Deacon
2012-07-26 16:49 ` Catalin Marinas
2012-07-26 16:01 ` [PATCH 2/2] ARM: mm: use 5 bits for swapfile type encoding Will Deacon
2012-07-26 16:49 ` Catalin Marinas
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=1343318468-10412-1-git-send-email-will.deacon@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).