linux-kernel - Re: sysfs/udev broken in latest git?

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:	Tue, 24 Jul 2007 13:55:17 +0200
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Simon Arlott" <simon@...e.lp0.eu>
Cc:	"Greg KH" <gregkh@...e.de>,
	"Cornelia Huck" <cornelia.huck@...ibm.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: sysfs/udev broken in latest git?

On 7/24/07, Simon Arlott <simon@...e.lp0.eu> wrote:
> On Tue, July 24, 2007 10:20, Kay Sievers wrote:
> > On 7/24/07, Greg KH <gregkh@...e.de> wrote:
> >> On Tue, Jul 24, 2007 at 10:03:14AM +0200, Cornelia Huck wrote:
> >> > On Tue, 24 Jul 2007 00:25:40 -0700,
> >> > Greg KH <gregkh@...e.de> wrote:
> >> >
> >> > > On Tue, Jul 24, 2007 at 07:39:38AM +0100, Simon Arlott wrote:
> >> > > > The following commit appears to break some of my udev rules (I don't
> >> > > > have the time to finish the bisect right now, but there's only four
> >> > > > changes showing in "git bisect visualize" - this one is tagged
> >> > > > bisect/bad, and the other three are docs/docs/unrelated).
> >> > > >
> >> > > > Neither of these symlinks get created by udev on kernels marked bad
> >> > > > (see bisect log below):
> >> > > >
> >> > > > ACTION=="add", \
> >> > > >         KERNEL=="event*", \
> >> > > >         SUBSYSTEM=="input", \
> >> > > >         SYSFS{description}=="i8042 KBD port", \
> >> > > >         NAME="input/%k", \
> >> > > >         SYMLINK="input/i8042-kbd", \
> >> > > >         MODE="0640", \
> >> > > >         GROUP="event"
> >> > > >
> >> > > > ACTION=="add", \
> >> > > >         KERNEL=="event*", \
> >> > > >         SUBSYSTEM=="input", \
> >> > > >         SYSFS{manufacturer}=="Logitech", \
> >> > > >         SYSFS{product}=="USB-PS/2 Optical Mouse", \
> >> > > >         NAME="input/%k", \
> >> > > >         SYMLINK="input/logitech-mouse", \
> >> > > >         MODE="0640", \
> >> > > >         GROUP="event"
> >
> > Simon, please run:
> >   udevinfo --attribute-walk --path=<devpath>
> > for the mouse on the working and the non-working kernel.
>
> On the working kernel:
>
>   looking at device '/devices/pci0000:00/0000:00:0c.0/usb2/2-2/2-2:1.0':

Please start with the event* device your rule catches, not the usb one.

Thanks,
Kay
-
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/