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
