linux-mips
[Top] [All Lists]

mprotect(PROT_NONE) doesn't prevent reading/writing on 2.6.14 Au1550

To: linux-mips@linux-mips.org
Subject: mprotect(PROT_NONE) doesn't prevent reading/writing on 2.6.14 Au1550
From: Clem Taylor <clem.taylor@gmail.com>
Date: Mon, 12 Dec 2005 16:34:03 -0500
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=t1v/0hYabmjPKtBVNoXhBs37j7dSeWDLUMCJk8dmPkUc+uR/yGiFI9zIGBMYHWPMfDR+5WK4eVXiOGcg6ZhdDWATku+Fe42uyATsXoxx97i3mzr82CiOdZPZzNZBdE0dBmUFOuuIBsFgw8IL7t0LA7g8NsfZRkaRezpzREVHX8o=
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org
Hi,

It seems that mprotect(PROT_NONE) isn't actually doing anything on my
2.6.14 au1550 system.

Attached is a simple test that allocates 64K (64K aligned),
reads/writes the buffer, mprotect(PROT_NONE) the buffer and then
attempts to read and write to the buffer a second time. I expected
that writing to a PROT_NONE page would result in a segfault, but on
the Au1550 the program runs without faulting. Running the same code on
x86 (2.6.13) segfaults as expected.

Is there some reason why mprotect() wouldn't work on the Au1550, or is
this a bug?

                                         Thanks,
                                         Clem Taylor

Attachment: mprotectTest.c
Description: Text Data

<Prev in Thread] Current Thread [Next in Thread>