| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20100129181024.GA12934@suse.de> Date: Fri, 29 Jan 2010 10:10:24 -0800 From: Greg KH <gregkh@...e.de> To: Peter Zijlstra <peterz@...radead.org> Cc: "Eric W. Biederman" <ebiederm@...ssion.com>, Cong Wang <amwang@...hat.com>, linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org>, Miles Lane <miles.lane@...il.com>, Heiko Carstens <heiko.carstens@...ibm.com>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Larry Finger <Larry.Finger@...inger.net>, akpm@...ux-foundation.org Subject: Re: [Patch 0/2] sysfs: fix s_active lockdep warning On Fri, Jan 29, 2010 at 06:57:28PM +0100, Peter Zijlstra wrote: > On Fri, 2010-01-29 at 06:22 -0800, Greg KH wrote: > > > > Heh, this whole mess is the very reason we didn't add lockdep support to > > the driver core. Nested devices that all look alike from the driver > > core, are really different objects and the locking lifetimes are > > separate, but lockdep can't see that. > > And here I through Alan Stern had a handle on making the driver core > play nice. It's not the driver core that is the issue here, it's that lockdep can't handle the tree structure of devices that is represented in the kernel. I don't think it is a driver core problem, but rather, a lockdep issue. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists