From owner-freebsd-current Mon Jan 18 12:29:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05412 for freebsd-current-outgoing; Mon, 18 Jan 1999 12:29:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05391 for ; Mon, 18 Jan 1999 12:29:44 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id PAA19180; Mon, 18 Jan 1999 15:29:11 -0500 (EST) Date: Mon, 18 Jan 1999 15:29:11 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Mike Smith cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: kernel malloc and M_CANWAIT In-Reply-To: <199901182020.MAA18399@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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? > > -- > \\ 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 > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message