| 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
| ||
|
Date: Tue, 13 Mar 2007 17:08:27 -0400 From: "Dmitry Torokhov" <dmitry.torokhov@...il.com> To: "Hugh Dickins" <hugh@...itas.com> Cc: "Alan Stern" <stern@...land.harvard.edu>, "Oliver Neukum" <oneukum@...e.de>, "Maneesh Soni" <maneesh@...ibm.com>, gregkh@...e.de, "Richard Purdie" <rpurdie@...ys.net>, "James Bottomley" <James.Bottomley@...eleye.com>, "Linus Torvalds" <torvalds@...ux-foundation.org>, "Kernel development list" <linux-kernel@...r.kernel.org> Subject: Re: 2.6.21-rc suspend regression: sysfs deadlock On 3/13/07, Hugh Dickins <hugh@...itas.com> wrote: > On Tue, 13 Mar 2007, Alan Stern wrote: > > > > On the other hand, a quick survey of the kernel source shows that > > DEVICE_ATTR is used over 1500 times. Auditing all of them is not a job > > for the faint-of-heart! > > Indeed, and faint-hearted Hugh wasn't intending to do so: but > stout-hearted Alan will need to, won't he, before his patch can go in? > I think we could rely on subsystems maintainers to let us know if there are potential problems. For example I can tell that neither input, serio nor gameport subsystems use sysfs to destroy their devices (action on sysfs may cause some other device to be destroyed but that should be ok, only self-destruction is not allowed, right?) -- Dmitry - 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