The print comes when the ‘current lock owner’ of a kernel resource is current CPU. I don’t know what could lead to this condition. Couldn’t find much on the net. Anyone debugged this?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The print comes when the ‘current lock owner’ of a kernel resource is current CPU. I don’t know what could lead to this condition. Couldn’t find much on the net. Anyone debugged this?
Ok, Got it.
This typically happens when you enter the same function twice, referencing to the same kernel resource, in a single execution context of the linux kernel (e.g. a single instance of softIRQ, etc).
The way out of this is to make sure you don’t re-enter the function twice in the same execution context. It’s a bug in your code if this happens.