Date: Wed, 7 Feb 2001 08:10:03 -0800 (PST) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: freebsd-bugs@FreeBSD.org Subject: Re: i386/24886: Cant msync memory mapped file onto desk. Message-ID: <200102071610.f17GA3674752@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/24886; it has been noted by GNATS. From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: "Iyad Qumei" <ikqumei@computer.org> Cc: freebsd-gnats-submit@freebsd.org Subject: Re: i386/24886: Cant msync memory mapped file onto desk. Date: Wed, 7 Feb 2001 11:07:07 -0500 (EST) <<On Wed, 7 Feb 2001 00:06:13 -0800, "Iyad Qumei" <ikqumei@computer.org> said: > The man pages confirmed to me your response, so I could conclude > that FreeBSD is more strict that Redhat Linux!? It's possible that you have found a bug in whatever version of the Linux kernel you were running. The POSIX standard states: If MAP_PRIVATE is specified, modifications to the mapped data by the calling process shall be visible only to the calling process and shall not change the underlying object. It is unspecified whether modifications to the underlying object done after the MAP_PRIVATE mapping is established are visible through the MAP_PRIVATE mapping. FreeBSD implements this behavior as described. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102071610.f17GA3674752>