From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Wed, 07 Nov 2007 06:53:39 +0000 Subject: Re: Calling kobject_uevent directly Message-Id: <20071107065339.GA22201@kroah.com> List-Id: References: <58b503a50711062152x3e3cedafxde62c964174a3e53@mail.gmail.com> In-Reply-To: <58b503a50711062152x3e3cedafxde62c964174a3e53@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Tue, Nov 06, 2007 at 09:52:36PM -0800, Tom wrote: > For devices with attributes that may change, is it "correct" to call > kobject_uevent directly with KOBJ_CHANGE in order to notify userspace? Yes. And what attribute do you want to do this for? > (This appears to be the behavior used in the drivers/mmc/host/omap.c driver) > > The KOBJ_ADD and KOBJ_REMOVE actions have comments saying "exclusive > to core". Is this policy or is there a technical reason? Both. lots of userspace stuff happens when these events are sent, so don't be sending them unless you really think you know what you are doing. And even then, please run the kernel patch by me and Kay to ensure that nothing bad will happen. Do you have a reason why you would want to do this? thanks, greg k-h ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel