On Wednesday 14 April 2010 23:04:03 J. Bruce Fields wrote: > The lockd thread is entirely under the BKL--it takes it at the top of > fs/lockd/svc.c:lockd(), and drops it at the bottom. It's possible > there may be code that lockd runs that assumes mutual exclusion with > code in locks.c, but I don't know. That one seems interesting as the lockd thread calls lots of sleeping functions as well as file lock code that takes the BKL again, both of which of course is not allowed when converting to a spinlock. I just attempted to blindly convert lockd to taking lock_flocks() in place of the BKL and releasing it where necessary, but quickly gave up because this seems rather pointless. It basically never does anything interesting between places where it would need to drop the lock. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
