Possible vmopar bug? (was malloc deadlock with M_NOWAIT)

VM gurus: This seems to be bug! This morning I sent an email (attached below) regarding a hang at the "vmopar" state. While waiting for responses, I use Google Advanced Groups Search looking for "vmopar" in all FreeBSD archived mailing lists and I did find the following message posted by Xavie

malloc deadlock with M_NOWAIT

I am trying to allocate a dynamic number of large memory (128K) by malloc(128K, M_xxx, M_NOWAIT). Although this is not done in an interrupt routine, I figure I'd better use M_NOWAIT so that I can deal with the situation when the memory is low. However, I experience the following deadlock: #1 0