From owner-freebsd-current Mon Jan 18 12:33:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05856 for freebsd-current-outgoing; Mon, 18 Jan 1999 12:33:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05847 for ; Mon, 18 Jan 1999 12:33:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA18468; Mon, 18 Jan 1999 12:29:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901182029.MAA18468@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: Mike Smith , Julian Elischer , current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-reply-to: Your message of "Mon, 18 Jan 1999 15:29:11 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Jan 1999 12:29:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 18 Jan 1999, Mike Smith wrote: > > > > > > > Here at whistle we are trying to remember about a conversation > > > regarding malloc that occured recently. Maybe others can help. > > > > > > There was some talk about the fact that malloc(..M_CANWAIT) > > > can now return with a failure. Is that true? > > > > Yes; it's necessary to do this to allow some chance of avoiding > > deadlock. > > Ouch! Is everything in src-sys already checking the return value of an M_WAITOK? Probably not, no. I had some patches from Andrzej who was trying to do it just for the mbuf allocator case; there's definitely a call for someone to take the time to clean things up. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message