linux-kernel - Re: [RFC] bind/unbind uevent

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:	Wed, 8 Dec 2010 11:18:27 +0100 (CET)
From:	Sebastian Ott <sebott@...ux.vnet.ibm.com>
To:	Kay Sievers <kay.sievers@...y.org>
cc:	Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: [RFC] bind/unbind uevent

On Tue, 7 Dec 2010, Kay Sievers wrote:
> On Tue, Dec 7, 2010 at 19:33, Greg KH <gregkh@...e.de> wrote:
> > On Tue, Dec 07, 2010 at 06:29:37PM +0100, Sebastian Ott wrote:
> 
> >> So I'm searching for a trigger when these attributes are created, or
> >> in other words when the device is useable, which I think translates to
> >> when a driver is bound to this device.
> >
> > Again, KOBJ_ADD is the correct one.
> >
> > If your driver is creating sysfs attributes on its own, that's a bug and
> > should be fixed.
> 
> Sounds a bit like the driver should create its own child device with
> its own properties, instead of mangling around with attributes at a
> device it binds to.

Yes, I get that feeling too. But I'm talking about existing drivers
and I don't think I can change their whole structure.

> 
> Sebastian, care to be more specific about the problem and bus in
> question. We should avoid new generic events. In some special cases,
> sending out 'change' from the driver might be acceptable, but it's
> usually not what we would suggest.

The specific problem I'm facing is about network drivers on S390.
They don't have one network adaptor, but deal with multiple devices
(e.g. a read, write and a data channel). To handle this we create
a group device to combine these devices. Triggered from userspace,
a network driver will create a group device and wait for itself to
bind to it (and adds his attributes inside his probe function).

Now some udev scripts expect these attributes at the time they
receive the add event. I don't want each network driver to throw
their own change events. So I guess I should go for the bus specific
change event. An other option would be to delay the add event..
which would be ugly, but has the advantage that we don't need to
change the udev scripts (which are distributor specific).

Regards,
Sebastian
--
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/