From owner-freebsd-current Mon Jan 26 22:27:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18841 for current-outgoing; Mon, 26 Jan 1998 22:27:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18830; Mon, 26 Jan 1998 22:27:04 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id BAA27440; Tue, 27 Jan 1998 01:26:45 -0500 (EST) (envelope-from toor) Message-Id: <199801270626.BAA27440@dyson.iquest.net> Subject: Re: Another observation on -current and NFS In-Reply-To: <199801270559.AAA07933@skynet.ctr.columbia.edu> from Bill Paul at "Jan 27, 98 00:59:37 am" To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Tue, 27 Jan 1998 01:26:45 -0500 (EST) Cc: grog@lemis.com, current@FreeBSD.ORG, dyson@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Bill Paul said: > > John Dyson made a couple of commits this weekend which I _thought_ would > fix this thing; I gave him a sample program that triggers the bug to help > him track it down. Assuming that he got my sample program to work, I'm > guessing there's more than one way to trigger the condition. > The fixes explicitly fixed the problem with the test code. There indeed must be more problems. I will look at it while it is still in my brain-cache. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig.