On 2013/10/14 16:06, Markus Blank-Burian wrote: > The crash utility indicated, that the lock was held by a kworker > thread, which was idle at the moment. So there might be a case, where > no unlock is done. I am trying to reproduce the problem at the moment > with CONFIG_PROVE_LOCKING, but without luck so far. It seems, that my > test-job is quite bad at reproducing the bug. I'll let you know, if I > can find out more. > Thanks. I'll review the code to see if I can find some suspect. PS: I'll be travelling from 10/16 ~ 10/28, so I may not be able to spend much time on this. -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
