> Yup. It's the problem. It locks, then calls some alloc routines, which
> fills a cache and uses kmalloc with GFP_KERNEL.
Thats quite common. If it can safely sleep there without other deadlocks a
semaphore may be better
> Turning it into GFP_ATOMIC might not be the best idea as the HFS
> filesystem currently shares a single hfs_malloc() for everybody and
> turning it into GFP_ATOMIC would cause all of HFS allocs to be atomic.
Another approach is to prealloc the object and pass it in, then free it
if not needed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jun 30 2001 - 21:00:22 EST