From owner-freebsd-current Sun Jan 5 14: 8:34 2003 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 9549037B401 for ; Sun, 5 Jan 2003 14:08:33 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A767143EA9 for ; Sun, 5 Jan 2003 14:08:32 -0800 (PST) (envelope-from phk@freebsd.org) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id h05M8JAS011724; Sun, 5 Jan 2003 23:08:26 +0100 (CET) (envelope-from phk@freebsd.org) To: Bruce Evans Cc: current@freebsd.org Subject: Re: specfs lock plumbing broken From: phk@freebsd.org In-Reply-To: Your message of "Mon, 06 Jan 2003 07:09:35 +1100." <20030106065245.O345-100000@gamplex.bde.org> Date: Sun, 05 Jan 2003 23:08:19 +0100 Message-ID: <11723.1041804499@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20030106065245.O345-100000@gamplex.bde.org>, Bruce Evans writes: >No. Also no INVARIANTS and the like. A profiling kernel (with profiling >not running) seemed to panic faster. Ok, in this case listening to KASSERTS would probably have helped you. Please try 1.351 of vfs_bio.c -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message