From owner-freebsd-current Tue May 28 22:37:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 0F3BF37B40A for ; Tue, 28 May 2002 22:37:38 -0700 (PDT) Received: from pool0116.cvx21-bradley.dialup.earthlink.net ([209.179.192.116] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #2) id 17Cw9E-0006QS-00; Tue, 28 May 2002 22:37:24 -0700 Message-ID: <3CF468F0.EDECFE43@mindspring.com> Date: Tue, 28 May 2002 22:36:48 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: Richard Wenninger , current@FreeBSD.ORG Subject: Re: UMA lock References: <20020529040704.A8A96380A@overcee.wemm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Peter Wemm wrote: > The bug is that things are calling things like malloc with M_WAITOK when > waiting is explicitly not allowed. There are other functions that can > tsleep as well that we have not added checks for yet, so this is likely > just the tip of the iceberg. :-( Why is this a problem? M_WAITOK does not mean that it will wait indefinitely, even though you'd think it would mean that, given the name... I think _sleeping_ is a problem, but allocation with M_WAITOK shouldn't be, given it's strange definition of "waiting". This is one of those hacks that John Baldwin was talking about earlier... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message