From owner-freebsd-current@FreeBSD.ORG  Mon Jun 16 10:20:28 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1EB7737B401
	for <freebsd-current@FreeBSD.org>;
	Mon, 16 Jun 2003 10:20:28 -0700 (PDT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5952F43F85
	for <freebsd-current@FreeBSD.org>;
	Mon, 16 Jun 2003 10:20:27 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h5GHKHM7049413;
	Mon, 16 Jun 2003 10:20:23 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200306161720.h5GHKHM7049413@gw.catspoiler.org>
Date: Mon, 16 Jun 2003 10:20:17 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: jesse@wingnet.net
In-Reply-To: <bcksi9$1to$1@main.gmane.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-current@FreeBSD.org
Subject: Re: qmail uses 100% cpu after FreeBSD-5.0 to 5.1 upgrade
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jun 2003 17:20:28 -0000

On 16 Jun, Jesse Guardiani wrote:

> I run qmail on my 4.8 servers.
> 
> For my sanity, is this a problem in 5.1-RELEASE, or in code after 5.1-RELEASE?
> We haven't upgraded to 5.1 yet (and don't intend to for a while), but I thought
> I'd ask since this bug would cripple our mail server.

It was broken in 5.1-CURRENT shortly after 5.1-RELEASE, until I
committed a patch a few minutes ago.  5.1-RELEASE is fine.  The
problematic versions of fifo_vnops.c are 1.87 and 1.88.