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:	Thu, 27 Jul 2006 13:12:55 -0700
From:	Greg KH <gregkh@...e.de>
To:	Andrew Morton <akpm@...l.org>
Cc:	ajwade@...001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com,
	andrew.j.wade@...il.com, linux-kernel@...r.kernel.org
Subject: Re: Kubuntu's udev broken with 2.6.18-rc2-mm1

On Thu, Jul 27, 2006 at 12:56:55PM -0700, Andrew Morton wrote:
> On Fri, 28 Jul 2006 15:46:08 -0400
> Andrew James Wade <andrew.j.wade@...il.com> wrote:
> 
> > Hello,
> > 
> > Some change between -rc1-mm2 and -rc2-mm1 broke Kubuntu's udev
> > (079-0ubuntu34). In particular /dev/mem went missing, and /dev/null had
> > bogus permissions (crw-------). I've kludged around the problem by
> > populating /lib/udev/devices from a good /dev, but I'm assuming the
> > breakage was unintentional.
> > 
> 
> /dev/null damage is due to a combination of vdso-hash-style-fix.patch and
> doing the kernel build as root (don't do that).
> 
> I don't know what happened to /dev/mem.

Me either.  Look in /sys/class/mem/  Is it full of symlinks or real
directories?

If symlinks, your version of udev should be able to handle it properly,
but might have a bug somehow.

Try running udevmonitor and echo a "1" to /sys/class/mem/mem/uevent and
see if udev creates the device properly or not.

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/