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:	Sun, 30 Jul 2006 23:00:33 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Greg KH <greg@...ah.com>
Cc:	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

On Sun, 30 Jul 2006 22:15:47 -0700
Greg KH <greg@...ah.com> wrote:

> On Sun, Jul 30, 2006 at 09:50:25PM -0700, Andrew Morton wrote:
> > On Sun, 30 Jul 2006 21:35:42 -0700
> > Greg KH <greg@...ah.com> wrote:
> > 
> > > Remember, FC3 is now in Legacy support mode, not something the mainline
> > > kernel should have to worry about.
> > 
> > It's not specifically related to FC3.  It's udev - we've broken _any_
> > distribution which uses a two-year-old udev.  In fact we're proposing
> > breaking any distro which has an older-than-ten-month udev.  That's really
> > bad.
> 
> Why?  What do you propose we do then?  Wait a year?  Two years?

Greg, once we put an interface into the kernel and expose it to userspace,
that's it - we support it forever.  At least, that's the model.  Yes,
sometimes in cases of necessity where we cannot feasibly support old
userspace we'll break things, with long notice and considerable thought
and care.

The impact is lower in this case because we've already trained our
long-suffering users to expect udev to regularly break.

> And that's the only group of people who would try to do this.
> Seriously, I don't see the complaint here.  It's an unsupported distro
> by the very makers of that distro.  How long should the community have
> to care about a distro after the creators of it have abandonded it?

Please stop going on about FC3.  My (repeat) point is that we're proposing
to break _all_ distros which are older than ten months.  We don't play the
"oh, that isn't supported any more" game.

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

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