Bosko Milekic wrote:
>
> fakepg_zone should probably be UMA_ZONE_VM. Or the vm_object lock
> needs to be dropped before allocating or freeing to that zone.
>
> What does Alan think? (cc'd)
>
Perhaps. Regardless, in this case, the lock-order reversal is a false
positive. What it shows is t
Try the attached patch.
On Fri, Aug 01, 2003 at 11:02:49AM +, Bosko Milekic wrote:
>
> fakepg_zone should probably be UMA_ZONE_VM. Or the vm_object lock
> needs to be dropped before allocating or freeing to that zone.
>
> What does Alan think? (cc'd)
>
> -Bosko
>
> On Thu, Jul 31, 20
fakepg_zone should probably be UMA_ZONE_VM. Or the vm_object lock
needs to be dropped before allocating or freeing to that zone.
What does Alan think? (cc'd)
-Bosko
On Thu, Jul 31, 2003 at 04:46:06PM -0700, Lars Eggert wrote:
> Hi,
>
> with yesterday's -current:
>
> 1st 0xc6dfd094 vm ob
Hi,
with yesterday's -current:
1st 0xc6dfd094 vm object (vm object) @ /usr/src/sys/vm/vm_object.c:434
2nd 0xc082f110 system map (system map) @ /usr/src/sys/vm/vm_kern.c:323
Stack backtrace:
backtrace(c032000b,c082f110,c033362f,c033362f,c03334c6) at backtrace+0x17
witness_lock(c082f110,8,c03334c