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 21:22:27 -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 20:37:57 -0700
Greg KH <greg@...ah.com> wrote:

> On Sun, Jul 30, 2006 at 10:27:06PM -0400, Andrew James Wade wrote:
> > On Sunday 30 July 2006 20:03, Greg KH wrote:
> > > Something's really broken with that version of udev then, because the
> > > 094 version I have running here works just fine with these symlinks.
> > 
> > Maybe, but some really odd things were happening in /sys with the
> > patch. I could still follow the bogus symlinks. More than that
> > 
> > /sys/class/mem/mem$ cd ../../class
> > and
> > /sys/class/mem/mem$ cd ../..
> > 
> > _both_ ended up with a $PWD of /sys/class.
> 
> Ick, ok, the problem is that my "virtual device" patch isn't in my
> "public" patch set that Andrew pulls from.  It will fix this issue up.
> I'll work on cleaning it up to be used by everyone tomorrow and move it
> to the tree that Andrew pulls from.  Then the next -mm release should
> have this issue fixed.

Mutter.  This stuff breaks my FC3 test box and there is, afaict, no clear
way for users to upgrade udev to unbreak it.

As a developer I could of course bang on things until it works, but that's
not the point.  The point is that these patches break Linux on a major
release from a major vendor only two years after its release.  That's not a
minor problem, is it?
-
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/