From owner-freebsd-current Thu Jul 8 4:20:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat195.34.mpoweredpc.net [142.177.195.34]) by hub.freebsd.org (Postfix) with ESMTP id 623AE154F5; Thu, 8 Jul 1999 04:20:22 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id IAA28701; Thu, 8 Jul 1999 08:20:37 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 8 Jul 1999 08:20:37 -0300 (ADT) From: The Hermit Hacker To: freebsd-current@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Known MMAP() race conditions ... ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Three weeks ago, I, and a few other INN administrators, posted about FreeBSD -STABLE's inability to run the newest INN code, due to MMAP() race conditions...essentially, after X hours of run time, on a heavily loaded INN server, the whole thing locks up solid. At that time, Matt pop'd up and stated that he knew of *at least* 6 MMAP() related race conditions that he was hoping to be able to get fixed "within a week"...that would have been two weeks ago. I've been watching the -commit messages closely, and CVSup'ng a new kernel almost daily, in the hopes of seeing some MMAP() related activity from someone, and haven't seen anything so far, so I'm curious as to whether or not anyone *but* Matt is aware of these race conditions, and/or is working on this? I'm trying to push moving some Solaris boxes at work over to FreeBSD, with our INN server being the 'safest' example to move over first, but there is no way I can do that with the current INN/FreeBSD interaction :( Thanks... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message