Date: Wed, 15 Oct 2003 14:44:01 +0200 From: Marius Strobl <marius@alchemy.franken.de> To: Alan Cox <alc@cs.rice.edu> Cc: cvs-src@freebsd.org Subject: Re: cvs commit: src/sys/vm vm_fault.c Message-ID: <20031015144401.I40718@newtrinity.zeist.de> In-Reply-To: <20031015084043.GR27527@cs.rice.edu>; from alc@cs.rice.edu on Wed, Oct 15, 2003 at 03:40:43AM -0500 References: <200310150800.h9F80j13045191@repoman.freebsd.org> <20031015084043.GR27527@cs.rice.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 15, 2003 at 03:40:43AM -0500, Alan Cox wrote: > On Wed, Oct 15, 2003 at 01:00:45AM -0700, Alan Cox wrote: > > alc 2003/10/15 01:00:45 PDT > > > > FreeBSD src repository > > > > Modified files: > > sys/vm vm_fault.c > > Log: > > - vm_fault_copy_entry() should not assume that the source object contains > > every page. If the source entry was read-only, one or more wired pages > > could be in backing objects. > > - vm_fault_copy_entry() should not set the PG_WRITEABLE flag on the page > > unless the destination entry is, in fact, writeable. > > > > Revision Changes Path > > 1.181 +19 -5 src/sys/vm/vm_fault.c > > This fixes the problem with mlockall() and cdrecord. > What was the general usability of mlockall() before this commit? I was told about at least two other programs that triggered a panic when using mlockall(). If this commit denotes the first working mlockall() would you be so kind as to bump the __FreeBSD_version?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031015144401.I40718>