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]

Message-ID: <AANLkTinmuxDYU9-zGvWB0mDDuXZEfZnuVxtSYGk62c8P@mail.gmail.com>
Date:	Tue, 7 Dec 2010 20:00:36 +0100
From:	Kay Sievers <kay.sievers@...y.org>
To:	Greg KH <gregkh@...e.de>
Cc:	Sebastian Ott <sebott@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] bind/unbind uevent

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.

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.

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/