From: chrubis-AlSwsSmVLrQ@public.gmane.org
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] mmap.2: Add note about partial page in BUGS section
Date: Wed, 27 Feb 2013 15:10:33 +0100 [thread overview]
Message-ID: <20130227141033.GA1797@rei> (raw)
In-Reply-To: <CAKgNAkjjtKkhrwqw4n-0C1oJOzSrF=3ducpb3K0ouo8BFVbEzQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi!
> I also tweaked the patch a little. The most notable change is that I
> changed your reference to "shm ipc" to "POSIX shared memory". Please
> let me know if that was incorrect.
>
> POSIX specifies that the system shall always zero fill any par???
> tial page at the end of the object and that system will never
> write any modification of the object beyond its end. On Linux,
> when you write data to such partial page after the end of the
> object, the data stays in the page cache even after the file is
> closed and unmapped and even though the data is never written
> to the file itself, subsequent mappings may see the modified
> content. In some cases, this could be fixed by calling
> msync(2) before the unmap takes place; however, this doesn't
> work on tmpfs (for example, when using POSIX shared memory
> interface documented in shm_overview(7)).
Thanks, that is better.
And out of curiosity, where is the most current man-pages git repo?
There seems to be github one and kernel.org one and they are out of
sync.
--
Cyril Hrubis
chrubis-AlSwsSmVLrQ@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-02-27 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 11:25 [PATCH] mmap.2: Add note about partial page in BUGS section chrubis-AlSwsSmVLrQ
[not found] ` <20121112112544.GC6764-J5syqNJeCN7twjQa/ONI9g@public.gmane.org>
2013-02-25 8:00 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkiK9FOSBsTuuC=kdkdg60z9WEAr67VEzubsJ065BCVCCQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-25 8:05 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkjjtKkhrwqw4n-0C1oJOzSrF=3ducpb3K0ouo8BFVbEzQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-27 14:10 ` chrubis-AlSwsSmVLrQ [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=20130227141033.GA1797@rei \
--to=chrubis-alswssmvlrq@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).