From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: enable PTE type bit in the mask for pte_modify
Date: Wed, 25 Feb 2015 16:43:20 +0000 [thread overview]
Message-ID: <20150225164319.GF1105@localhost> (raw)
In-Reply-To: <1424821221-16396-1-git-send-email-fkan@apm.com>
On Tue, Feb 24, 2015 at 03:40:21PM -0800, Feng Kan wrote:
> Caught during Trinity testing. The pte_modify does not allow
> modification for PTE type bit. This cause the test to hang
> the system. It is found that the PTE can't transit from an
> inaccessible page (b00) to a valid page (b11) because the mask
> does not allow it. This happens when a big block of mmaped
> memory is set the PROT_NONE, then the a small piece is broken
> off and set to PROT_WRITE | PROT_READ cause a huge page split.
>
> Signed-off-by: Feng Kan <fkan@apm.com>
It looks fine to me. Thanks.
I wonder whether mprotect() to change between PROT_NONE and an
accessible protection ever worked (I thought we tested this).
--
Catalin
prev parent reply other threads:[~2015-02-25 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 23:40 [PATCH] arm64: enable PTE type bit in the mask for pte_modify Feng Kan
2015-02-25 16:43 ` Catalin Marinas [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=20150225164319.GF1105@localhost \
--to=catalin.marinas@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 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.