Date: Wed, 4 Apr 2012 15:35:57 -0400 From: John Baldwin <jhb@freebsd.org> To: Julian Elischer <julian@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Gleb Smirnoff <glebius@freebsd.org>, src-committers@freebsd.org Subject: Re: svn commit: r233745 - head/sys/netinet/ipfw Message-ID: <201204041535.57453.jhb@freebsd.org> In-Reply-To: <4F7CA1CA.8070602@freebsd.org> References: <201203311120.q2VBKmJT099513@svn.freebsd.org> <201204040757.42452.jhb@freebsd.org> <4F7CA1CA.8070602@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, April 04, 2012 3:32:26 pm Julian Elischer wrote: > On 4/4/12 4:57 AM, John Baldwin wrote: > > On Tuesday, April 03, 2012 7:46:56 pm Julian Elischer wrote: > >> On 3/31/12 4:20 AM, Gleb Smirnoff wrote: > >> > >> > >> Many years ago there was the possibility that malloc M_WAITOK could > >> return on shutdown or in some other rare error cases. > >> > >> Are we certain this is no longer true? > > That hasn't been true in a long while. In edge cases malloc() with M_WAITOK > > will just panic rather than return NULL. (e.g. "kmem too small") > > > what happens if you call reboot while it is waiting for free space? The same thing that happens to any other thread asleep when we reboot, they eventually die one way or another when the CPU resets. If it happens to be a user thread that doesn't respond to kill then you get a warning about not all processes dying during shutdown, but that's about it. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201204041535.57453.jhb>