make PROT_WRITE imply PROT_READ
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 10 lines · Alan Cox
Ar Gwe, 2006-06-30 am 10:35 +0200, ysgrifennodd Arjan van de Ven:
Quoted 4 lines
apps like JVM's forgot
PROT_EXECand break when the hardware enforces it apps that forgetPROT_READbreak when the kernel/hardware enforce itnot too much difference....
There is quite a difference. The
_EXECcase behaves predictably for the platforms that support it. At least I am not aware of cases that is not true. The_READcase without the fault handling patch behaves
predictable on platforms that support it, but since you're testing on a platform where it isn't fully supported, it behaves
Quoted 2 lines
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.
Signature · 4 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF verbreiteten Lügen zu sabotieren. http://david.woodhou.se/why-not-spf.html
Ar Sad, 2006-07-01 am 15:19 +0200, ysgrifennodd Bodo Eggert:
Quoted 8 lines
Quoted 2 lines
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
Quoted 5 lines · Alan Cox
Ar Sad, 2006-07-01 am 15:19 +0200, ysgrifennodd Bodo Eggert:
Quoted 3 lines
Quoted 2 lines
unpredictably depending on the precise ordering of events on a clean page.
Quoted 7 lines
Quoted 5 lines
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
I'm talking about the affected platforms.
Quoted 6 lines
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.
IMO it's the best we can get, even if the results are ...
Quoted 1 line
That gets quite random and has bizarre effects.
OTOH, there is not much difference between randomly wrong and consistently wrong, so I shall be happy either way (as if it would even matter).
Signature · 1 line
'Calm down -- it's only ones and zeros.'