From owner-freebsd-current@FreeBSD.ORG Sat Aug 16 00:12:35 2003 Return-Path: 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 15EB937B401; Sat, 16 Aug 2003 00:12:35 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 161B743FE3; Sat, 16 Aug 2003 00:12:34 -0700 (PDT) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h7G7CSlX018473; Sat, 16 Aug 2003 09:12:28 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: Robert Watson From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 15 Aug 2003 23:01:50 EDT." Date: Sat, 16 Aug 2003 09:12:27 +0200 Message-ID: <18472.1061017947@critter.freebsd.dk> cc: current@freebsd.org cc: Kris Kennaway Subject: Re: LOR with filedesc structure and Giant X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Aug 2003 07:12:35 -0000 In message , Robe rt Watson writes: > >On Fri, 15 Aug 2003, Kris Kennaway wrote: > >> The problem seems to be due to select() being called on the /dev/null >> device, and it is holding the filedesc lock when it reaches >> PICKUP_GIANT() in spec_poll. > >Yeah, this is pretty much the same issue you've been bumping into for a >bit -- we hold filedesc lock over select(), which means every object we >poll can't grab a lock that either comes before the file descriptor lockin >the lock order, or that might sleep. Doesn't this effectively doom any attempt at getting rid af Giant from below ? -- 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.