From: Andrew Morton <akpm@digeo.com>
To: Dave McCracken <dmccr@us.ibm.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5.66-mm2] Fix page_convert_anon locking issues
Date: Wed, 2 Apr 2003 15:38:45 -0800 [thread overview]
Message-ID: <20030402153845.0770ef54.akpm@digeo.com> (raw)
In-Reply-To: <102170000.1049325787@baldur.austin.ibm.com>
Dave McCracken <dmccr@us.ibm.com> wrote:
>
> > i_shared_sem won't stop that. The pte points into thin air, and may now
> > point at a value which looks like our page.
>
> Once we find a match in the pte entry, we have the additional protection of
> the pte_chain lock. The pte entry is never cleared without a call to
> page_remove_rmap, which will block on the pte_chain lock.
But:
+ /* Double check to make sure the pte page hasn't been freed */
+ if (!pmd_present(*pmd))
+ goto out_unmap;
+
==> munmap, pte page is freed, reallocated for pagecache, someone
happens to write the correct value into it.
+ if (page_to_pfn(page) != pte_pfn(*pte))
+ goto out_unmap;
+
+ if (addr)
+ *addr = address;
+
> >> Because the page is in transition from !PageAnon to PageAnon.
> >
> > These are file-backed pages. So what does PageAnon really mean?
>
> I suppose PageAnon should be renamed to PageChain, to mean it's using
> pte_chains. It did mean anon pages until I used it for nonlinear pages.
OK, I'll edit the diffs at a convenient time.
> >> We have to
> >> hold the pte_chain lock during the entire transition in case someone else
> >> tries to do something like page_remove_rmap, which would break.
> >
> > How about setting PageAnon at the _start_ of the operation?
> > page_remove_rmap() will cope with that OK.
>
> Hmm... I was gonna say that page_remove_rmap will BUG() if it doesn't find
> the entry, but it's only under DEBUG and could easily be changed.
That debug already triggers if it is enabled. I forget why, but it's OK.
> Lemme
> think on this one a bit. I need to assure myself it's safe to go unlocked
> in the middle.
Thanks. It's tricky. I wish we had more tests for this stuff, and real
applications which use it...
--
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:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-04-02 23:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 17:13 Dave McCracken
2003-04-02 21:29 ` Andrew Morton
2003-04-02 21:56 ` Dave McCracken
2003-04-02 23:09 ` Andrew Morton
2003-04-02 23:23 ` Dave McCracken
2003-04-02 23:38 ` Andrew Morton [this message]
2003-04-02 23:42 ` Dave McCracken
2003-04-02 23:52 ` Andrew Morton
2003-04-02 23:58 ` Dave McCracken
2003-04-03 14:49 ` Dave McCracken
2003-04-03 15:38 ` Hugh Dickins
2003-04-03 16:00 ` Dave McCracken
2003-04-03 16:33 ` Hugh Dickins
2003-04-03 16:39 ` Dave McCracken
2003-04-03 20:00 ` Andrew Morton
2003-04-03 20:06 ` Andrew Morton
2003-04-03 20:56 ` Andrew Morton
2003-04-03 21:01 ` Dave McCracken
2003-04-02 23:59 ` Hugh Dickins
2003-04-03 0:06 ` Hugh Dickins
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=20030402153845.0770ef54.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=dmccr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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