From: Manfred Spraul <manfred@colorfullife.com>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kmalloc without GFP_xxx?
Date: Wed, 29 Jun 2005 22:28:23 +0200 [thread overview]
Message-ID: <42C30467.8060900@colorfullife.com> (raw)
Denis wrote:
>It struck me that kernel actually can figure out whether it's okay
>to sleep or not by looking at combination of (flags & __GFP_WAIT)
>and ((in_atomic() || irqs_disabled()) as it already does this for
>might_sleep() barfing:
>
Wrong:
- the kernel cannot figure out if a thread owns a normal spinlock():
in_atomic detects spin_lock_bh(), irqs_disabled spin_lock_irq(). But
spin_lock has no global state.
- dito for get_cpu()/put_cpu users.
- dito for rcu users, or anyone else that uses preempt_disable() for
whatever purpose
--
Manfred
next reply other threads:[~2005-06-29 20:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 20:28 Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-29 20:44 kmalloc without GFP_xxx? Manfred Spraul
2005-06-30 5:57 ` Steven Rostedt
2005-06-29 11:02 Denis Vlasenko
2005-06-29 11:15 ` Jens Axboe
2005-06-29 11:18 ` Denis Vlasenko
2005-06-29 11:25 ` Jens Axboe
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
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=42C30467.8060900@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.