From mboxrd@z Thu Jan  1 00:00:00 1970
From: daniel.baluta@gmail.com (Daniel Baluta)
Date: Fri, 4 Nov 2011 00:04:52 +0200
Subject: spin_lock behavior
In-Reply-To: <CAAFf3B8S_3iZ1-TKdekKprQ1vuuMHwdJABPLtuYrkbcyxOhEcA@mail.gmail.com>
References: <CAAFf3B8S_3iZ1-TKdekKprQ1vuuMHwdJABPLtuYrkbcyxOhEcA@mail.gmail.com>
Message-ID: <CAEnQRZALcmrSGmHb-qD+FOm97MwxBcKDZ1zKR2PSwEH+VBKZbg@mail.gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

Hello,

> I wrote a sample module which looked like this and i expected the module to
> hang as i have used 2 spin_lock simultaneously. But i find the print after
> the second spin_lock being printed and the module works perfectly fine. Can
> any body please help me in understanding this? I got this problem from a
> driver i wrote and had a typo "spin_lock" instead of "spin_unlock" the
> driver worked fine and i caught the mistake only during a review

Are you running your tests on an UP with preemption disabled?

thanks,
Daniel.