Invalid locking pattern in Documentation/kernel-hacking/locking.rst?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear documentation maintainers,

the latest version of locking.rst contains the following (since 2005):

"Manfred Spraul points out that you can still do this, even if the data
is very occasionally accessed in user context or softirqs/tasklets. The
irq handler doesn't use a lock, and all other accesses are done as so::

        spin_lock(&lock);
        disable_irq(irq);
"

Isn't it "sleeping in atomic" actually because of the sleeping
disable_irq()?

-- 
Alexander Sverdlin
Siemens AG
www.siemens.com




[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux