Re: kobject events questions

From: Greg KH (greg_at_kroah.com)
Date: 09/30/04

  • Next message: Randy.Dunlap: "Re: udev is too slow creating devices"
    Date:	Wed, 29 Sep 2004 16:35:07 -0700
    To: Timo Ter?s <ext-timo.teras@nokia.com>
    
    

    On Wed, Sep 29, 2004 at 04:37:26PM +0300, Timo Ter?s wrote:
    > Hi all,
    >
    > I've been following the evolution of kobject events patch. This is
    > because I'd like to implement a netfilter target that is able to send an
    > event to userland using it.
    >
    > There's a small description of it and some background in the netfilter
    > mailing list:
    > http://lists.netfilter.org/pipermail/netfilter-devel/2004-August/016342.html
    >
    > Now that the events are strictly associated with kobjects (the original
    > patch had a way to send arbitrary events) I have two choices:
    >
    > 1) Send the events so that they are always associated with the network
    > devices class_device kobject. I guess this would be quite clean way to
    > do it, but it'd require adding a new signal type and would limit the
    > iptables target to be associated always with a interface.
    >
    > 2) Create a device class that has virtual timer devices that trigger
    > events (ie. /sys/class/utimer). Each timer could have some attributes
    > (like expired, expire_time, etc.) and would emit "change" signals
    > whenever timer expires.
    >
    > I'd like to hear what you think of the thing I'm trying to do?

    Have you looked at the "connector" patch from Evgeniy Polyakov
    <johnpol@2ka.mipt.ru> that was posted to Linux kernel? After that goes
    in, the kevent code will probably be tweaked to use that interface.

    thanks,

    greg k-h
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Randy.Dunlap: "Re: udev is too slow creating devices"

    Relevant Pages

    • Re: [linux-usb-devel] [PATCH] back out sysfs reference count change
      ... >> The patch below backs out Maneesh's sysfs patch that was recently added ... > kobject that didn't bump the module ref count. ... > that's the whole point of the module reference count. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH} fix defect with kobject memory leaks during del_gendisk
      ... >> Comments are welcome as to whether or not this patch is the right ... >> which deletes the gendisk, delete the children kobjects, and delete the ... If the kobject has a ktype release function, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [linux-usb-devel] [PATCH] back out sysfs reference count change
      ... > The patch below backs out Maneesh's sysfs patch that was recently added ... > kobject has its reference finally released (usually after the module ... that's the whole point of the module reference count. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH} fix defect with kobject memory leaks during del_gendisk
      ... kobject. ... > This patch changes the functionality so the release function (in this ... lifetime longer than the time between add_diskand del_gendisk. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] Mark kobjects as unitialized
      ... On Monday 10 March 2008 09:22:00 pm Greg KH wrote: ... AFAICS the best way to solve this is by fixing the kobject users ... how about this patch instead? ... But we should fix the sys_device users later, ...
      (Linux-Kernel)