Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965891Ab0BZTgf (ORCPT ); Fri, 26 Feb 2010 14:36:35 -0500 Received: from iolanthe.rowland.org ([192.131.102.54]:35660 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S965854Ab0BZTgd (ORCPT ); Fri, 26 Feb 2010 14:36:33 -0500 Date: Fri, 26 Feb 2010 14:36:30 -0500 (EST) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Thomas Gleixner cc: Greg KH , Peter Zijlstra , "Eric W. Biederman" , Cong Wang , Kernel development list , Tejun Heo , Miles Lane , Heiko Carstens , Benjamin Herrenschmidt , Larry Finger , Andrew Morton Subject: Re: [Patch 0/2] sysfs: fix s_active lockdep warning In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 925 Lines: 24 On Thu, 4 Feb 2010, Thomas Gleixner wrote: > On Thu, 4 Feb 2010, Greg KH wrote: > > > However in view of the other difficulties, it still doesn't seem > > > possible to make device mutexes work with lockdep. I suggest removing > > > Thomas's patch. > > > > Unless Thomas or anyone else thinks of something that can solve these > > problems, I will do so. > > Hmm, I have not seen those lockdep splats on -rt where we have the > mutex conversion for quite some time already. Need to look at it. Thomas, did you ever figure out what was going on? It would be nice to know why the -rt kernels don't have any lockdep problems associated with the device mutexes. Alan Stern -- 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/