Date: Tue, 17 Feb 2004 01:37:22 +0000 From: Colin Percival <colin.percival@wadham.ox.ac.uk> To: Maxime Henrion <mux@FreeBSD.org> Cc: Dag-Erling Smorgrav <des@FreeBSD.org> Subject: Re: cvs commit: src/sys/vm vm_kern.c Message-ID: <6.0.1.1.1.20040217013021.03a47a30@imap.sfu.ca> In-Reply-To: <20040216210503.GC35475@elvis.mu.org> References: <Pine.NEB.3.96L.1040216140303.63057O-100000@fledge.watson.org> <28938.1076959003@critter.freebsd.dk> <20040216210503.GC35475@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 21:05 16/02/2004, Maxime Henrion wrote: >I find it very convenient to have a flag to tell malloc() to try as hard >as it can to allocate the memory without crashing on us. <hat="kernel newbie"> Is this really good enough? When I was routinely running my system out of kernel memory by using a large malloc backed md(4), the panic never came from a failed allocation in the md code; rather, md would use up all the available memory, and then some other kernel call (which needed only some small amount of memory) would panic. From a security point of view, I can't see how there's any alternative to using a user-allocated buffer for such requests. </hat> Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.1.1.1.20040217013021.03a47a30>