From owner-freebsd-bugs Wed Feb 7 8:10:23 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7775437B4EC for ; Wed, 7 Feb 2001 08:10:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f17GA3674752; Wed, 7 Feb 2001 08:10:03 -0800 (PST) (envelope-from gnats) Date: Wed, 7 Feb 2001 08:10:03 -0800 (PST) Message-Id: <200102071610.f17GA3674752@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Garrett Wollman Subject: Re: i386/24886: Cant msync memory mapped file onto desk. Reply-To: Garrett Wollman Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR i386/24886; it has been noted by GNATS. From: Garrett Wollman To: "Iyad Qumei" 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) < 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