From owner-freebsd-current  Mon Jan 18 14:16:16 1999
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA21762
          for freebsd-current-outgoing; Mon, 18 Jan 1999 14:16:16 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21757
          for <current@FreeBSD.ORG>; Mon, 18 Jan 1999 14:16:12 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA18275;
	Tue, 19 Jan 1999 09:16:06 +1100
Date: Tue, 19 Jan 1999 09:16:06 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199901182216.JAA18275@godzilla.zeta.org.au>
To: bde@zeta.org.au, julian@whistle.com
Subject: Re: kernel malloc and M_CANWAIT
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> Of course not.  It is fundamental that malloc(..., M_WAITOK) either
>> succeeds or panics.  Most callers depend on this and don't check for
>> success.  The others are bogus.
>
>actually it turns out to be true..

Actually not.

>see other email from matt.

See my corrections to that mail.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message