From: Valdis.Kletnieks@vt.edu
To: Arnd Bergmann <arnd@arndb.de>
Cc: michal.simek@petalogix.com, Paul Mundt <lethal@linux-sh.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
LTP <ltp-list@lists.sourceforge.net>,
John Williams <john.williams@petalogix.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Grant Likely <grant.likely@secretlab.ca>,
subrata@linux.vnet.ibm.com
Subject: Re: mmap syscall problem
Date: Mon, 06 Jul 2009 20:44:57 -0400 [thread overview]
Message-ID: <105602.1246927497@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 06 Jul 2009 16:16:11 +0200." <200907061616.12220.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On Mon, 06 Jul 2009 16:16:11 +0200, Arnd Bergmann said:
> What happens in a simple user space program that mmaps the same
> page to two addresses? Something like
>
> #include <sys/mman.h>
> #include <fcntl.h>
> int main(void)
> {
> int fd = open("existing-4k-file", O_RDWR);
> char *p1 = mmap(0, 4096, PROT_READ | PROT_WRITE,
> MAP_SHARED, fd, 0);
> char *p2 = mmap(p1 + 4096, 4096, PROT_READ | PROT_WRITE,
> MAP_SHARED | MAP_FIXED, fd, 0);
>
> *p1 = 0xaa; *p2 = 0x55;
>
> return *p1; /* returns 0xaa if broken, 0x55 if correct */
> }
Strictly speaking, doesn't that need a barrier of some sort between the two
assignments? I mean, how is gcc supposed to intuit that p1 and p2 alias
each other and it needs to reload *p1 before returning that value?
(And in more complicated code, I could even see the compiler re-ordering those
two assignments, so the in-file value is different as well as the return; value)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
prev parent reply other threads:[~2009-07-07 0:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 12:37 Michal Simek
2009-07-03 15:02 ` Arnd Bergmann
2009-07-06 6:32 ` Michal Simek
2009-07-06 8:05 ` Arnd Bergmann
2009-07-06 12:07 ` Michal Simek
2009-07-06 12:14 ` Paul Mundt
2009-07-06 12:54 ` Michal Simek
2009-07-06 14:16 ` Arnd Bergmann
2009-07-06 14:43 ` Michal Simek
2009-07-06 15:05 ` Arnd Bergmann
2009-07-06 15:19 ` Michal Simek
2009-07-07 0:44 ` Valdis.Kletnieks [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=105602.1246927497@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=john.williams@petalogix.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=michal.simek@petalogix.com \
--cc=mingo@elte.hu \
--cc=subrata@linux.vnet.ibm.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
all inboxes | Powered by JetHome®