panic: ffs_valloc: dup alloc

While stress testing GENERIC (+ QUOTA) HEAD from May 14 06:55 UTC I
got this panic:

mode = 040770, inum = 193745, fs = /tmp
panic: ffs_valloc: dup alloc
cpuid = 3
KDB: enter: panic
[thread pid 18041 tid 100219 ]
Stopped at      kdb_enter+0x2b: nop
db> where
Tracing pid 18041 tid 100219 td 0xc43dd510
kdb_enter(c0907dc2) at kdb_enter+0x2b
panic(c091ef1c,c091eefb,41f8,2f4d1,c382c0d4) at panic+0x14b
ffs_valloc(c51f1924,81b0,c3e61480,e66ce880,c4dc1618) at
ffs_valloc+0x152
ufs_makeinode(81b0,c51f1924,e66ceb90,e66ceba4) at ufs_makeinode+0x4e
ufs_create(e66cea14,0,e66ceb7c,e66cead0,c06f7258) at ufs_create+0x25
VOP_CREATE_APV(c09c23a0,e66cea14) at VOP_CREATE_APV+0x7e
vn_open_cred(e66ceb7c,e66cec7c,1b0,c3e61480,3) at vn_open_cred+0x1c0
vn_open(e66ceb7c,e66cec7c,1b0,3,0) at vn_open+0x1e
kern_open(c43dd510,bfbfe720,0,602,1b0) at kern_open+0xb9
open(c43dd510,e66ced04,e66ceccc,c069896c,c43dd510) at open+0x18
syscall(2805003b,bfbf003b,bfbf003b,2805188c,bfbfe8f0) at syscall+0x27e

More info at http://people.freebsd.org/~pho/stress/log/cons202.html
-- 
Peter Holm