From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "corbet@lwn.net" <corbet@lwn.net>,
"manfred@colorfullife.com" <manfred@colorfullife.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Invalid locking pattern in Documentation/kernel-hacking/locking.rst?
Date: Fri, 9 Dec 2022 12:23:47 +0000 [thread overview]
Message-ID: <442ecdf402f8e726f2be4ab19c7299d272e27c0b.camel@siemens.com> (raw)
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
next reply other threads:[~2022-12-09 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 12:23 Sverdlin, Alexander [this message]
2022-12-09 18:47 ` Manfred Spraul
2022-12-12 14:43 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=442ecdf402f8e726f2be4ab19c7299d272e27c0b.camel@siemens.com \
--to=alexander.sverdlin@siemens.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®