All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Arjan van de Ven <arjan@infradead.org>,
	Nicolas Pitre <nico@cam.org>,
	Jes Sorensen <jes@trained-monkey.org>,
	Al Viro <viro@ftp.linux.org.uk>, Oleg Nesterov <oleg@tv-sign.ru>,
	David Howells <dhowells@redhat.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Christoph Hellwig <hch@infradead.org>, Andi Kleen <ak@suse.de>,
	Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [patch 08/19] mutex subsystem, core
Date: Tue, 3 Jan 2006 16:05:54 +0100	[thread overview]
Message-ID: <20060103150554.GA1211@elte.hu> (raw)
In-Reply-To: <43BA78EC.7050603@yahoo.com.au>


* Nick Piggin <nickpiggin@yahoo.com.au> wrote:

> >+#define spin_lock_mutex(lock)			spin_lock(lock)
> >+#define spin_unlock_mutex(lock)			spin_unlock(lock)
> 
> Is this an interrupt deadlock, or do you not allow interrupt contexts 
> to even trylock a mutex?

correct, no irq contexts are allowed. This is also checked for if 
CONFIG_DEBUG_MUTEXES is enabled.

	Ingo

  reply	other threads:[~2006-01-03 15:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 10:08 [patch 08/19] mutex subsystem, core Ingo Molnar
2006-01-03 13:15 ` Nick Piggin
2006-01-03 15:05   ` Ingo Molnar [this message]
2006-01-03 15:38     ` Linus Torvalds
2006-01-03 15:42       ` Ingo Molnar
2006-01-03 18:00 ` Oleg Nesterov
2006-01-03 16:49   ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2006-01-03 16:46 Ingo Molnar
2006-01-03 15:58 Kai Geek
2006-01-02 16:34 Ingo Molnar

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=20060103150554.GA1211@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=dhowells@redhat.com \
    --cc=hch@infradead.org \
    --cc=jes@trained-monkey.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=nico@cam.org \
    --cc=oleg@tv-sign.ru \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=torvalds@osdl.org \
    --cc=viro@ftp.linux.org.uk \
    /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.