linux-kernel - Re: A standardized way of reporting kernel events to userspace

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 28 May 2011 08:26:32 +0800
From:	Greg KH <greg@...ah.com>
To:	Arvid Brodin <arvid.brodin@...a.com>
Cc:	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
	Juergen Beisert <jbe@...gutronix.de>
Subject: Re: A standardized way of reporting kernel events to userspace

On Sat, May 28, 2011 at 01:04:49AM +0200, Arvid Brodin wrote:
> Hi,
> 
> After I asked on linux-usb for a way for userspace to catch over-current events
> on the usb bus, it turned out that Juergen Beisert had had the need to do the
> exact same thing some time ago. He posted this patch using a uevent to notify
> userspace:

We've discussed why using uevents for this is not a good idea in the
past, and I don't think anything has changed since then.  You might want
to search the archives for details if you are curious.

As to other solutions, there's always netlink, and people have proposed,
seriously, to put dbus in the kernel to allow it to emit messages that
way.  I don't object to that, and I think there was even some patches
floating around to do that as well.  You might want to revive them and
see if that would fit your requirement here.

hope this helps,

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/