Date: Wed, 28 Apr 2004 22:53:36 +0200 From: Marius Strobl <marius@alchemy.franken.de> To: Brian Fundakowski Feldman <green@freebsd.org> Cc: current@freebsd.org Subject: Re: mlockall(2 fixed Message-ID: <20040428225336.E11722@newtrinity.zeist.de> In-Reply-To: <200404272254.i3RMscjL019357@green.homeunix.org>; from green@freebsd.org on Tue, Apr 27, 2004 at 06:54:37PM -0400 References: <200404272254.i3RMscjL019357@green.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 27, 2004 at 06:54:37PM -0400, Brian Fundakowski Feldman wrote: > Please try the following if you are having strange SIGBUS problems/leaked > wired memory and you are running programs that use mlockall(2). There were > several distinct bugs that caused pages to never get unwired and completely > unrelated processes to act as if mlockall(2) was called when they had not > done so. > This patch appears to fix the problems on the one box I could reproduce it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040428225336.E11722>