From owner-freebsd-current Tue Apr 4 6:34: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 8A18337B8A6 for ; Tue, 4 Apr 2000 06:34:03 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id PAA27237; Tue, 4 Apr 2000 15:33:43 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Brad Knowles Cc: Jeroen Ruigrok/Asmodai , Matthew Dillon , current@FreeBSD.ORG Subject: Re: 2nd call for reviews and tests: buf->bio patch In-reply-to: Your message of "Tue, 04 Apr 2000 14:15:56 +0200." Date: Tue, 04 Apr 2000 15:33:43 +0200 Message-ID: <27235.954855223@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Brad Knowles writes: >At 8:23 AM +0200 2000/4/4, Jeroen Ruigrok/Asmodai wrote: > >> Like I said in another mail, this is CURRENT, things are >> expected to break. You want stability of API's, go 3-STABLE. You want >> a somewhat stable environment, go 4-STABLE. 5 is bleeding edge, have >> your bandages ready. > > Like I said in a previous message, Poul broke vinum (among other >things) under 4.0-STABLE, and this needs to be fixed ASAP. If Poul >had kept his changes unique to -CURRENT, then 4.0-STABLE wouldn't >have been affected. But he didn't, and it was. Brad, You are confused. I have not made one single commit to 4.0-STABLE which even comes close to vinum. The problem in vinum/releng4 is the problem greg has been blaming on CAM since at least FreeBSDcon and indications seems to be that it is actually a malloc/free gottcha in vinum. I have nothing to do with that, apart from being releived that we don't seem to have a random stack-smasher bug in the system. Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message