Dan Carpenter <dan.carpenter@xxxxxxxxxx> wrote: > Thanks for the explanation. I misread the code and then managed to > trigger an unrelated locking bug and got confused. > > I think there is a spin_unlock(call->lock) missing somewhere on an > error path. I have attached a reproducer file. Are you running with lockdep enabled? That should catch such things. David -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
