From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: 7eggert@gmx.de
Cc: Arjan van de Ven <arjan@infradead.org>,
Ulrich Drepper <drepper@gmail.com>, Pavel Machek <pavel@ucw.cz>,
Jason Baron <jbaron@redhat.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: make PROT_WRITE imply PROT_READ
Date: Sun, 02 Jul 2006 10:56:11 +0100 [thread overview]
Message-ID: <1151834171.14346.2.camel@localhost.localdomain> (raw)
In-Reply-To: <E1FwfNo-00012H-Gz@be1.lrz>
Ar Sad, 2006-07-01 am 15:19 +0200, ysgrifennodd Bodo Eggert:
> > unpredictably depending on the precise ordering of events on a clean
> > page.
>
> You asked for a fault, and as long as the hardware supports it, you'll
> get one (and you're supposed to). If the hardware doesn't support read
> faults on mapped pages, you may not get all the read faults you want. The
> proposed patch makes the situation worse by disabeling the _requested_
> failures even in situations where it can be done.
The later patch as posted has no effect on such platforms because it
does not touch anything but the architecture code. Without that its
random what happens because the CPU cannot enforce write only but the
fault handler tries to. That means if you fault reading because the page
is not present you may get a fault while if you access a page which is
present you won't get a fault.
That gets quite random and has bizarre effects.
Alan
next prev parent reply other threads:[~2006-07-02 9:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6qIEW-1Tx-23@gated-at.bofh.it>
[not found] ` <6qIEW-1Tx-21@gated-at.bofh.it>
[not found] ` <6qUwd-2Aq-9@gated-at.bofh.it>
[not found] ` <6qUwd-2Aq-7@gated-at.bofh.it>
[not found] ` <6qUFV-2N8-13@gated-at.bofh.it>
[not found] ` <6qUFY-2N8-33@gated-at.bofh.it>
[not found] ` <6rlmT-8op-37@gated-at.bofh.it>
[not found] ` <6siwJ-3dC-5@gated-at.bofh.it>
[not found] ` <6sLoY-4GV-31@gated-at.bofh.it>
[not found] ` <6sZUS-V5-19@gated-at.bofh.it>
[not found] ` <6tib4-2wA-3@gated-at.bofh.it>
[not found] ` <6tmHL-Oq-5@gated-at.bofh.it>
[not found] ` <6tpZ7-5Tj-13@gated-at.bofh.it>
2006-07-01 13:19 ` make PROT_WRITE imply PROT_READ Bodo Eggert
2006-07-02 9:56 ` Alan Cox [this message]
2006-07-02 22:04 ` Bodo Eggert
[not found] <fa.PuMM6IwflUYh1MWILO9rb6z4fvY@ifi.uio.no>
2006-06-23 1:24 ` Robert Hancock
2006-06-23 13:39 ` Jason Baron
2006-06-23 14:06 ` Arjan van de Ven
2006-06-23 14:05 ` Jason Baron
2006-06-23 14:18 ` Arjan van de Ven
2006-06-24 18:45 ` Ulrich Drepper
2006-06-27 9:56 ` Pavel Machek
2006-06-27 12:18 ` Arjan van de Ven
2006-06-28 16:43 ` Ulrich Drepper
2006-06-28 19:49 ` Pavel Machek
2006-06-28 20:05 ` Chase Venters
2006-06-28 23:47 ` Ulrich Drepper
2006-06-29 7:30 ` Pavel Machek
2006-06-29 11:58 ` Alan Cox
2006-06-29 17:20 ` Pavel Machek
2006-06-29 21:00 ` Jason Baron
2006-07-07 2:05 ` Jason Baron
2006-06-30 3:49 ` Ulrich Drepper
2006-06-29 8:15 ` Arjan van de Ven
2006-06-30 3:48 ` Ulrich Drepper
2006-06-30 8:35 ` Arjan van de Ven
2006-06-30 12:20 ` Alan Cox
2006-06-22 17:33 Jason Baron
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=1151834171.14346.2.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=7eggert@gmx.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=drepper@gmail.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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