From: Ralf Baechle <ralf@linux-mips.org>
To: Clem Taylor <clem.taylor@gmail.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: can read/write to mprotect(PROT_NONE) region with 2.6.14 on au1550
Date: Thu, 2 Feb 2006 16:54:36 +0000 [thread overview]
Message-ID: <20060202165436.GB17352@linux-mips.org> (raw)
In-Reply-To: <ecb4efd10512071351scea736fg8d026e3fa3c54c79@mail.gmail.com>
On Wed, Dec 07, 2005 at 04:51:23PM -0500, Clem Taylor wrote:
> I was trying to use mprotect(PROT_NONE) to help debug a problem, and
> it seems that mprotect() isn't actually doing anything with my 2.6.14
> linux-mips kernel on an au1550. Attached is a simple test program that
> segfaults as expected on x86 (2.6.12), but does not segfault on mips
> (2.6.14). I can both read and write PROT_NONE memory without problem,
> which should result in a segfault. Originally, I was trying to
> mprotect() a mmaped GFP_DMA region which wasn't working and then I
> tried a simpler test that also wasn't working.
>
> Shouldn't mprotect() work? Could I be missing a config option, or is
> this just broken?
That's a defect in CONFIG_64BIT_PHYS_ADDR which unfortunately is need
on Alchemy SOCs due to the silly address space layout.
Ralf
next prev parent reply other threads:[~2006-02-02 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 21:51 can read/write to mprotect(PROT_NONE) region with 2.6.14 on au1550 Clem Taylor
2006-02-02 16:54 ` Ralf Baechle [this message]
2006-04-07 23:09 ` [PATCH] FIx mprotect() syscall for MIPS32 w/36-bit physical address support Sergei Shtylyov
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=20060202165436.GB17352@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=clem.taylor@gmail.com \
--cc=linux-mips@linux-mips.org \
/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