From: Andrew Morton <akpm@osdl.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: msync() needed before munmap() when writing to shared mapping?
Date: Fri, 16 Apr 2004 15:46:52 -0700 [thread overview]
Message-ID: <20040416154652.7ab27e79.akpm@osdl.org> (raw)
In-Reply-To: <20040416220223.GA27084@mail.shareable.org>
Jamie Lokier <jamie@shareable.org> wrote:
>
> I've followed the logic from do_munmap() and it looks good:
> unmap_vmas->zap_pte_range->page_remove_rmap->set_page_dirty.
>
> Can someone confirm this is correct, please?
yup, zap_pte_range() transfers pte dirtiness into pagecache dirtiness when
tearing down the mapping, leaving the dirty page floating about in
pagecache for kupdate/kswapd/fsync to catch. Longstanding behaviour.
next prev parent reply other threads:[~2004-04-16 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 22:02 msync() needed before munmap() when writing to shared mapping? Jamie Lokier
2004-04-16 22:46 ` Andrew Morton [this message]
2004-04-16 23:10 ` Jamie Lokier
2004-04-16 23:59 ` Andrew Morton
2004-04-16 23:55 ` Hugh Dickins
2004-04-17 20:23 ` H. Peter Anvin
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=20040416154652.7ab27e79.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.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