linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: hugh@veritas.com, linux-mm@kvack.org
Subject: Re: unuse_pte: set pte dirty if the page is dirty
Date: Mon, 27 Feb 2006 20:39:23 -0800	[thread overview]
Message-ID: <20060227203923.24e9336c.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0602272009100.15012@schroedinger.engr.sgi.com>

Christoph Lameter <clameter@engr.sgi.com> wrote:
>
> > There are cases (eg, mprotect) in which a subsequent page-dirtying is
> > "impossible".  Only we've now gone and made it possible.  The worst part of
> > it is that we're made it possible in exceedingly rare circumstances.
> 
> Yes we need to check the VM_WRITE bit like in maybe_mkwrite() in 
> memory.c.... Thanks...
> 

I dunno - I said I hadn't thought about it much.  But I'd like you guys to,
please - this is tricky stuff and bugs in there can reveal themselves in
horridly subtle ways.  We need to spend much time, care and thought over
each change.

>  static void unuse_pte(struct vm_area_struct *vma, pte_t *pte,
>  		unsigned long addr, swp_entry_t entry, struct page *page)
>  {
> +	pte_t new_pte = pte_mkold(mk_pte(page, vma->vm_page_prot));
> +
>  	inc_mm_counter(vma->vm_mm, anon_rss);
>  	get_page(page);
> +
>  	set_pte_at(vma->vm_mm, addr, pte,
> -		   pte_mkold(mk_pte(page, vma->vm_page_prot)));
> +			(PageDirty(page) && (vma->vm_flags & VM_WRITE)) ?
> +			pte_mkdirty(new_pte) : new_pte);
> +
>  	page_add_anon_rmap(page, vma, addr);
>  	swap_free(entry);

argh.  Whenever you find yourself thinking of the question-mark operator,
take a cold shower.

This?

--- devel/mm/swapfile.c~unuse_pte-set-pte-dirty-if-the-page-is-dirty	2006-02-27 20:33:19.000000000 -0800
+++ devel-akpm/mm/swapfile.c	2006-02-27 20:34:32.000000000 -0800
@@ -480,10 +480,16 @@ unsigned int count_swap_pages(int type, 
 static void unuse_pte(struct vm_area_struct *vma, pte_t *pte,
 		unsigned long addr, swp_entry_t entry, struct page *page)
 {
+	pte_t new_pte;
+
 	inc_mm_counter(vma->vm_mm, anon_rss);
 	get_page(page);
-	set_pte_at(vma->vm_mm, addr, pte,
-		   pte_mkold(mk_pte(page, vma->vm_page_prot)));
+
+	new_pte = pte_mkold(mk_pte(page, vma->vm_page_prot));
+	if (PageDirty(page) && (vma->vm_flags & VM_WRITE))
+		new_pte = pte_mkdirty(new_pte);
+	set_pte_at(vma->vm_mm, addr, pte, new_pte);
+
 	page_add_anon_rmap(page, vma, addr);
 	swap_free(entry);
 	/*
_

I think it has the same race - if the page gets cleaned and someone
mprotects the vma to remove VM_WRITE, we dirty an undirtiable page.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-02-28  4:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28  1:33 Christoph Lameter
2006-02-28  1:53 ` Andrew Morton
2006-02-28  1:57   ` Christoph Lameter
2006-02-28  2:21     ` Andrew Morton
2006-02-28  4:20       ` Christoph Lameter
2006-02-28  4:39         ` Andrew Morton [this message]
2006-02-28  5:32           ` Christoph Lameter
2006-02-28 14:05             ` Hugh Dickins
2006-02-28 16:06               ` Christoph Lameter

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=20060227203923.24e9336c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=clameter@engr.sgi.com \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.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