From owner-freebsd-hackers Fri Aug 7 21:03:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25034 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 21:03:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from burka.rdy.com (burka.rdy.com [205.149.163.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25029; Fri, 7 Aug 1998 21:03:53 -0700 (PDT) (envelope-from dima@burka.rdy.com) Received: (from dima@localhost) by burka.rdy.com (8.8.8/RDY&DVV) id VAA05702; Fri, 7 Aug 1998 21:03:24 -0700 (PDT) Message-Id: <199808080403.VAA05702@burka.rdy.com> Subject: Re: Does this mean we have another breakin? In-Reply-To: <199808080135.SAA00798@implode.root.com> from David Greenman at "Aug 7, 1998 6:35:55 pm" To: dg@root.com Date: Fri, 7 Aug 1998 21:03:24 -0700 (PDT) Cc: brett@lariat.org, roberto@keltia.freenix.fr, FreeBSD-security@FreeBSD.ORG, hackers@FreeBSD.ORG X-Class: Fast Organization: HackerDome Reply-To: dima@best.net From: dima@best.net (Dima Ruban) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman writes: > >We were about to do it AGAIN. Now we're holding out some hope that it's > >just a bug -- though perhaps the same one that's crashing us when we try to > >back up. > > > >In any event, I just received private e-mail stating that at least one > >person has encountered VM problems in -stable under heavy CPU loads when > >the swapper kicks in. According to the message, they cause corruption of > >file modification dates. > > Corruption is probably not the right word. There might be a bug where a > page is seen as modified when it isn't, causing the modify date to get > updated. The only way to be certain is to compare the binary with your > backup (e.g. if installed from CDROM, then with the copy on the CDROM). I > haven't personally seen this happen in more than a year, so if the bug is > still there, it must be fairly rare. We usually get this bug once in two weeks. But since file by itself stays the same and machine doesn't crash, fixing/finding the problem wasn't in out TODO list. > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe security" in the body of the message > -- dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message