linux-kernel - Re: [PATCH RFC] kobject_uevent: notify uevent sysfs file on changes

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, 16 May 2024 13:17:34 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rafael@...nel.org>,
	linux-kernel@...r.kernel.org, Sebastian Reichel <sre@...nel.org>,
	linux-pm@...r.kernel.org
Subject: Re: [PATCH RFC] kobject_uevent: notify uevent sysfs file on changes

On Thu, May 16, 2024 at 12:27:58PM +0200, Thomas Weißschuh wrote:
> The sysfs file "uevent" that exists for each device
> contains the same information that is attached to uevents emitted via
> netlink (or the usermode helper).
> This is useful for userspace which interacts with sysfs directly,
> without using (lib)udev.
> 
> However it is not possible to actually get notified when the data in
> the "uevent" file changes.

What is wrong with listening to the uevent that is happening when the
file changes?

> Enable these notifications, so that the "uevent" file can be used
> together with inotify and friends.

uevent files are meant to be listened to by the uevent itself, why not do
that?

thanks,

greg k-h