Date: Sat, 3 Jul 2004 14:22:46 -0400 From: Brian Fundakowski Feldman <green@freebsd.org> To: ticso@cicely.de Cc: bmilekic@freebsd.org Subject: Re: malloc(9) M_WAITOK broken Message-ID: <20040703182246.GA964@green.homeunix.org> In-Reply-To: <20040703101858.GB65870@cicely5.cicely.de> References: <20040703075555.GA65870@cicely5.cicely.de> <20040703101858.GB65870@cicely5.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 03, 2004 at 12:18:59PM +0200, Bernd Walter wrote: > On Sat, Jul 03, 2004 at 09:55:56AM +0200, Bernd Walter wrote: > > I get daily panics in vinum because malloc M_WAITOK returns NULL. > > Source is from 1st Jul running on alpha. > > Since vm_uma_core.c Rev 1.94 uma_zalloc_arg allways ignores M_WAITOK > in the non WITNESS case because badness is initialized as 1. > My understanding is that M_WAITOK shouldn't be ignored in any case > to avoid returning NULL - at least malloc(9) is documented to never > return NULL with M_WAITOK. Please try an updated src/sys/vm/uma_core.c now (the rest of the build is broken, so just try updating the last revision of that file.) -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040703182246.GA964>