From: Manfred Spraul <manfred@colorfullife.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kmalloc without GFP_xxx?
Date: Wed, 29 Jun 2005 22:44:10 +0200 [thread overview]
Message-ID: <42C3081A.1040108@colorfullife.com> (raw)
Hi,
One question from Linux-Tag was about the lack of documentation about/in
the kernel. I try to maintain docbook entries when I modify code, even
though I think it's mostly wasted time: Virtually noone reads it anyway,
instead armchair logic on lkml.
Steven wrote:
>Here we see that task 2 can spin with interrupts off, while the first task
>is servicing an interrupt, and God forbid if the IRQ handler sends some
>kind of SMP signal to the CPU running task 2 since that would be a
>deadlock. Granted, this is a hypothetical situation, but makes using
>spin_lock with interrupts enabled a little scary.
>
>
Not, it's not even a hypothetical situation. It's an explicitely
forbidden situation: SMP signals are sent with smp_call_function and the
documentation to that function clearly says:
*
* You must not call this function with disabled interrupts or from a
* hardware interrupt handler or from a bottom half handler.
*/
--
Manfred
next reply other threads:[~2005-06-29 20:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 20:44 Manfred Spraul [this message]
2005-06-30 5:57 ` kmalloc without GFP_xxx? Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2005-06-29 20:28 Manfred Spraul
2005-06-29 11:02 Denis Vlasenko
2005-06-29 11:15 ` Arjan van de Ven
2005-06-29 11:20 ` Denis Vlasenko
2005-06-29 11:37 ` Arjan van de Ven
2005-06-29 13:44 ` Steven Rostedt
2005-06-29 14:14 ` Denis Vlasenko
2005-06-29 14:23 ` Jörn Engel
2005-06-29 14:53 ` Steven Rostedt
2005-06-29 15:10 ` Jörn Engel
2005-06-29 15:48 ` Steven Rostedt
2005-06-29 15:54 ` Jörn Engel
2005-06-29 16:04 ` Steven Rostedt
2005-06-29 15:12 ` Oliver Neukum
2005-06-29 16:48 ` Timur Tabi
2005-06-29 17:22 ` Steven Rostedt
2005-06-29 17:43 ` Richard B. Johnson
2005-06-29 18:07 ` Steven Rostedt
2005-06-30 7:52 ` Denis Vlasenko
2005-06-30 8:05 ` Steven Rostedt
2005-06-30 1:02 ` Benjamin Herrenschmidt
2005-06-30 6:02 ` Steven Rostedt
2005-06-29 11:15 ` Jens Axboe
2005-06-29 11:18 ` Denis Vlasenko
2005-06-29 11:25 ` Jens Axboe
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=42C3081A.1040108@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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