linux-kernel - Re: Kubuntu's udev broken with 2.6.18-rc2-mm1

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 31 Jul 2006 12:14:12 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Andrew Morton <akpm@...l.org>
Cc:	Greg KH <greg@...ah.com>,
	ajwade@...001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com,
	laurent.riffard@...e.fr, andrew.j.wade@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: Kubuntu's udev broken with 2.6.18-rc2-mm1

Ar Sul, 2006-07-30 am 23:00 -0700, ysgrifennodd Andrew Morton:
> > > Are we going to stop doing this soon?
> > 
> > Not if we want to keep on making things better.  The real reason I made
> > these changes is to get power management working better.  We need to get
> > the devices into the proper place in the sysfs tree in order to handle
> > suspend/resume for classes of devices properly.  That's what Linus's
> > patch did, and now I'm moving the devices to allow it to really happen.
> > 
> 
> This sucks.  Do you know what machines we'll be breaking out there?  I
> sure don't.

Greg, this changeset should get ripped out and thrown away. Its wrong.
Its an API breakage and it is going to catch a lot of people. People
said at the kernel summit the sysfs had serious problems because of the
structure it exposes and you said you could use symlinks and the like to
work around it, or fix the code.

How about proving it or doing the work to make it possible rather than
continuing to break everything repeatedly.

Alan

-
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/