| To: | Clem Taylor <clem.taylor@gmail.com> |
|---|---|
| Subject: | Re: mprotect(PROT_NONE) doesn't prevent reading/writing on 2.6.14 Au1550 |
| From: | Pete Popov <ppopov@embeddedalley.com> |
| Date: | Mon, 12 Dec 2005 20:52:36 -0800 |
| Cc: | "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org> |
| In-reply-to: | <ecb4efd10512121334g6713d30ftf5a351fc61f1b6bd@mail.gmail.com> |
| Organization: | Embedded Alley Solutions, Inc |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <ecb4efd10512121334g6713d30ftf5a351fc61f1b6bd@mail.gmail.com> |
| Reply-to: | ppopov@embeddedalley.com |
| Sender: | linux-mips-bounce@linux-mips.org |
On Mon, 2005-12-12 at 16:34 -0500, Clem Taylor wrote: > 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? Do you have another MIPS system you can test this on? Pete |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | mprotect(PROT_NONE) doesn't prevent reading/writing on 2.6.14 Au1550, Clem Taylor |
|---|---|
| Next by Date: | To put Linux kernel as closer as possible to 0x80000000, colin |
| Previous by Thread: | mprotect(PROT_NONE) doesn't prevent reading/writing on 2.6.14 Au1550, Clem Taylor |
| Next by Thread: | To put Linux kernel as closer as possible to 0x80000000, colin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |