From: Nishanth Aravamudan <nacc@us.ibm.com>
To: libhugetlbfs-devel@lists.sourceforge.net, linuxppc-dev@ozlabs.org
Subject: Re: [Libhugetlbfs-devel] libbugetlbfs: Test case for powerpc huge_ptep_set_wrprotect() bug
Date: Mon, 7 Jul 2008 11:48:53 -0700 [thread overview]
Message-ID: <20080707184853.GA19240@us.ibm.com> (raw)
In-Reply-To: <20080707071955.GA27709@yookeroo.seuss>
On 07.07.2008 [17:19:55 +1000], David Gibson wrote:
> Until very recently (in fact, even now in mainline) powerpc kernels
> had a bug in huge_ptep_set_wrprotect() which meant the 'huge' flag was
> not passed down to pte_update() and hpte_need_flush(). This meant the
> hash ptes for hugepages would not be correctly flushed on fork(),
> allowing the parent to pollute the child's mapping after the fork().
>
> This patch adds a testcase to libhugetlbfs for this behaviour, also
> doing some other checking of the COW semantics over a fork().
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Applied, thanks,
Nish
--
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center
prev parent reply other threads:[~2008-07-07 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 7:19 libbugetlbfs: Test case for powerpc huge_ptep_set_wrprotect() bug David Gibson
2008-07-07 15:27 ` [Libhugetlbfs-devel] " Adam Litke
2008-07-07 18:48 ` Nishanth Aravamudan [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=20080707184853.GA19240@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=libhugetlbfs-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.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).