Andrew Gallatin wrote:
Ugh. Since it may call kmem_malloc(), UMA must hold Giant.
This is the same problem the mbuf system has, and its what's
keeping network device drivers under Giant in 5.0.
Both subsytems should probably have GIANT_REQUIRED at all entry
points so as to catch locking
Ugh. Since it may call kmem_malloc(), UMA must hold Giant.
This is the same problem the mbuf system has, and its what's
keeping network device drivers under Giant in 5.0.
Both subsytems should probably have GIANT_REQUIRED at all entry
points so as to catch locking problems like this earlier.
