Subject: Re: lock bug in getnewvnode, or uvm_km_kmemalloc/uvm_map ?
To: Manuel Bouyer <bouyer@antioche.eu.org>
From: Andrew Brown <atatat@atatdot.net>
List: tech-kern
Date: 11/20/2002 23:21:47
>so here is my proposed fix to this problem.
>There are a few interface changes:
>- amap_extend() gains a flags parameter, can be either M_NOWAIT or M_WAITOK
> (amap_extend() use malloc)
yes, amap_extend() uses malloc, but at the same time, it will only get
called from a process context when extending an amap. kernel map
entries don't use amaps.
i haven't really looked closely at the raid autoconfig stuff, but i
don't think it involves a "process", so this part seems like an
unnecessary change.
--
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org * "ah! i see you have the internet
twofsonet@graffiti.com (Andrew Brown) that goes *ping*!"
werdna@squooshy.com * "information is power -- share the wealth."