From owner-freebsd-current Fri Sep 25 15:59:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01177 for freebsd-current-outgoing; Fri, 25 Sep 1998 15:59:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01170 for ; Fri, 25 Sep 1998 15:59:09 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA28308; Fri, 25 Sep 1998 15:59:01 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd028284; Fri Sep 25 15:58:53 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id PAA22094; Fri, 25 Sep 1998 15:58:52 -0700 (MST) From: Terry Lambert Message-Id: <199809252258.PAA22094@usr04.primenet.com> Subject: Re: VM out-of-swap problems To: kkennawa@physics.adelaide.edu.au (Kris Kennaway) Date: Fri, 25 Sep 1998 22:58:52 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: from "Kris Kennaway" at Sep 25, 98 11:26:34 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is anyone actively working on the problems related to daemons dying after the > system has used a large amount of swap (the old "inetd() in realloc: junk > pointer" thing)? It seems to me that with the release just around the corner > this is something which should be killed now, as it seems to be an easily > repeatable problem for many people and would adversely impact many servers in > the real world (e.g. potential DoS risk). This is known to be related to the mmap/normal-file buffer problems; specifically, a page of the executing image gets corrupted. So long as there are instances of the page cached, then you are screwed. There are at least three know bugs in this code, with one of them fixed by applying strained bits of the last Dyson mega-patch (the one that implemented CPU affinit for kernel threads, and other experimental things, at the same time). I am currently tracking one of them down, slowly (the "random processes SIG-11 during normal operation, but only on 486DX clock multiplied processors" bug). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message