Ticketing spinlocks - How to get to the owner who locked the spinlock?

[manty kuma]

Thank you Sanjeev,

But as of now i am not sure on how to reproduce the issue. So i have to
deal with the dump.

Regards,
Manty

On Tue, Jan 27, 2015 at 3:17 PM, sanjeev sharma <sanjeevsharmaengg at gmail.com
> wrote:

> Hello
>
> you can try to print running task backtrack information in kernel/lockdep.c
>
> Regards
> Sanjeev Sharma
>
> On Tue, Jan 27, 2015 at 11:27 AM, manty kuma <mantykuma at gmail.com> wrote:
>
>> Hi All,
>>
>> Currently I am looking into an issue which is holding the printk
>> lock(logbuf_lock)
>>
>> logbuf_lock = {
>>   raw_lock = {
>>     owner = 0,
>>     next = 4
>>   }
>> }
>>
>> I read about ticketing spinlocks to understand the above output. I
>> understood that 4 cpu's are waiting for the lock while someone already has
>> it.
>>
>> I would like to know who has it? Is there a way I can know which process
>> is acquiring a given spinlock? Is the information not stored in it?
>>
>> I am using crash tool to analyse the dump
>>
>> Regards,
>> Manty
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150127/e93b5edf/attachment.html