From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH 1/12]: MUTEX: Implement mutexes From: James Bottomley In-Reply-To: References: <200512162313.jBGND7g4019623@warthog.cambridge.redhat.com> <1134791914.13138.167.camel@localhost.localdomain> <14917.1134847311@warthog.cambridge.redhat.com> <20051218092616.GA17308@flint.arm.linux.org.uk> Content-Type: text/plain Date: Sun, 18 Dec 2005 13:41:26 -0600 Message-Id: <1134934887.3517.15.camel@mulgrave> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit To: Linus Torvalds Cc: Russell King , Nicolas Pitre , David Howells , Steven Rostedt , linux-arch@vger.kernel.org, lkml , mingo@redhat.com, Andrew Morton List-ID: On Sun, 2005-12-18 at 10:42 -0800, Linus Torvalds wrote: > It's easy enough to add a "might_sleep()" to the up(). Not strictly true, > but conceptually it would make sense to make up/down match in that sense. > We'd have to mark the (few) places that do down_trylock() + up() in > interrupt context with a special "up_in_interrupt()", but that would be ok > even from a documentation standpoint. Actually, I don't think you want might_sleep(): there are a few cases where we do an up() from under a spinlock, which will spuriously trigger this. I'd suggest WARN_ON(in_interrupt()) instead. James