From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Laurent Dufour <ldufour@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, xemul@parallels.com,
linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au,
aneesh.kumar@linux.vnet.ibm.com, paulus@samba.org
Cc: criu@openvz.org
Subject: Re: [PATCH 1/3] mm: clearing pte in clear_soft_dirty()
Date: Fri, 16 Oct 2015 20:30:05 +0530 [thread overview]
Message-ID: <1445007605.24309.25.camel@kernel.crashing.org> (raw)
In-Reply-To: <8352032008c7d9f1eee8d39599888a4cbe570bf7.1444995096.git.ldufour@linux.vnet.ibm.com>
On Fri, 2015-10-16 at 14:07 +0200, Laurent Dufour wrote:
> As mentioned in the commit 56eecdb912b5 ("mm: Use
> ptep/pmdp_set_numa()
> for updating _PAGE_NUMA bit"), architecture like ppc64 doesn't do
> tlb flush in set_pte/pmd functions.
>
> So when dealing with existing pte in clear_soft_dirty, the pte must
> be cleared before being modified.
Note that this is true of more than powerpc afaik. There's is a general
rule that we don't "restrict" a PTE access permissions without first
clearing it, due to various races.
> Signed-off-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
> CC: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> ---
> fs/proc/task_mmu.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
> index e2d46adb54b4..c9454ee39b28 100644
> --- a/fs/proc/task_mmu.c
> +++ b/fs/proc/task_mmu.c
> @@ -753,19 +753,20 @@ static inline void clear_soft_dirty(struct
> vm_area_struct *vma,
> pte_t ptent = *pte;
>
> if (pte_present(ptent)) {
> + ptent = ptep_modify_prot_start(vma->vm_mm, addr,
> pte);
> ptent = pte_wrprotect(ptent);
> ptent = pte_clear_flags(ptent, _PAGE_SOFT_DIRTY);
> + ptep_modify_prot_commit(vma->vm_mm, addr, pte,
> ptent);
> } else if (is_swap_pte(ptent)) {
> ptent = pte_swp_clear_soft_dirty(ptent);
> + set_pte_at(vma->vm_mm, addr, pte, ptent);
> }
> -
> - set_pte_at(vma->vm_mm, addr, pte, ptent);
> }
>
> static inline void clear_soft_dirty_pmd(struct vm_area_struct *vma,
> unsigned long addr, pmd_t *pmdp)
> {
> - pmd_t pmd = *pmdp;
> + pmd_t pmd = pmdp_huge_get_and_clear(vma->vm_mm, addr, pmdp);
>
> pmd = pmd_wrprotect(pmd);
> pmd = pmd_clear_flags(pmd, _PAGE_SOFT_DIRTY);
next prev parent reply other threads:[~2015-10-16 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 12:07 [PATCH 0/3] mm/powerpc: enabling memory soft dirty tracking Laurent Dufour
2015-10-16 12:07 ` [PATCH 1/3] mm: clearing pte in clear_soft_dirty() Laurent Dufour
2015-10-16 15:00 ` Benjamin Herrenschmidt [this message]
2015-10-17 12:12 ` Aneesh Kumar K.V
2015-10-16 12:07 ` [PATCH 2/3] mm: clear_soft_dirty_pmd requires THP Laurent Dufour
2015-10-17 12:14 ` Aneesh Kumar K.V
2015-10-16 12:07 ` [PATCH 3/3] powerpc/mm: Add page soft dirty tracking Laurent Dufour
2015-10-17 12:19 ` Aneesh Kumar K.V
2015-10-17 13:24 ` Benjamin Herrenschmidt
2015-10-16 21:11 ` [PATCH 0/3] mm/powerpc: enabling memory " Andrew Morton
2015-10-17 2:15 ` Benjamin Herrenschmidt
2015-10-17 12:07 ` Aneesh Kumar K.V
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=1445007605.24309.25.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=criu@openvz.org \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=xemul@parallels.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;
as well as URLs for NNTP newsgroup(s).