Subject: Re: mprotect(2) strange behaviour under compat linux
To: Nicolas Joly <>
From: David Laight <>
List: current-users
Date: 12/18/2007 18:14:51
On Tue, Dec 18, 2007 at 11:40:27AM +0100, Nicolas Joly wrote:
> Intrumenting uvm_fault.c show that protections are correct (check_prot
> = 0x2), but something (memset ?) is trying to access this area for
> reading (access_type = 0x1) ...
> Could this be a bug in memset from suse 10.0 glibc (from
> pkgsrc/emulators/suse100_base) ?

It actually seems likely that someone is assuming that PROT_WRITE
implies PROT_READ.

Actually, since the i386 (and probably the later parts) don't
support 'write only' mappings, maybe the compat netbsd32 mmap
should enforce read access if write access is requested.


David Laight: