Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932561AbVLPWmJ (ORCPT ); Fri, 16 Dec 2005 17:42:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932560AbVLPWmI (ORCPT ); Fri, 16 Dec 2005 17:42:08 -0500 Received: from smtp.osdl.org ([65.172.181.4]:52131 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S932543AbVLPWmG (ORCPT ); Fri, 16 Dec 2005 17:42:06 -0500 Date: Fri, 16 Dec 2005 14:41:16 -0800 (PST) From: Linus Torvalds To: Thomas Gleixner cc: Geert Uytterhoeven , Steven Rostedt , Andrew Morton , linux-arch@vger.kernel.org, Linux Kernel Development , matthew@wil.cx, arjan@infradead.org, Christoph Hellwig , mingo@elte.hu, Alan Cox , nikita@clusterfs.com, pj@sgi.com, dhowells@redhat.com Subject: Re: [PATCH 1/19] MUTEX: Introduce simple mutex implementation In-Reply-To: <1134772964.2806.50.camel@tglx.tec.linutronix.de> Message-ID: References: <20051215085602.c98f22ef.pj@sgi.com> <20051213143147.d2a57fb3.pj@sgi.com> <43A0AD54.6050109@rtr.ca> <20051214155432.320f2950.akpm@osdl.org> <17313.29296.170999.539035@gargle.gargle.HOWL> <1134658579.12421.59.camel@localhost.localdomain> <4743.1134662116@warthog.cambridge.redhat.com> <7140.1134667736@warthog.cambridge.redhat.com> <20051215112115.7c4bfbea.akpm@osdl.org> <1134678532.13138.44.camel@localhost.localdomain> <1134769269.2806.17.camel@tglx.tec.linutronix.de> <1134770778.2806.31.camel@tglx.tec.linutronix.de> <1134772964.2806.50.camel@tglx.tec.linutronix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 974 Lines: 27 On Fri, 16 Dec 2005, Thomas Gleixner wrote: > > Therefor, if you want to handle that "init protection" scenario, do not > use a mutex, because the owner can not be defined at compile - > allocation time. Sure it could. We certainly have "init_task", for example. It may or may not be the right thing to use, of course. Depends on what the situation is. > You can still implement (chose a mechanism) a mutex on top - or in case > of lack of priority inheritance or debugging with exactly the same - > mechanism as a semaphore, but this does not change the semantical > difference at all. "Friends don't let friends use priority inheritance". Just don't do it. If you really need it, your system is broken anyway. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/