linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: David Miller <davem@davemloft.net>,
	Marcel Holtmann <marcel@holtmann.org>,
	linux-hotplug@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] netdev: generate kobject uevent on network events.
Date: Mon, 24 Nov 2008 20:06:45 +0000	[thread overview]
Message-ID: <20081124120645.417ea6e7@extreme> (raw)
In-Reply-To: <ac3eb2510811241155h4f51784cgf44d2e3d7ae807b8@mail.gmail.com>

On Mon, 24 Nov 2008 20:55:02 +0100
"Kay Sievers" <kay.sievers@vrfy.org> wrote:

> On Mon, Nov 24, 2008 at 20:45, Stephen Hemminger <shemminger@vyatta.com> wrote:
> > It is easier for some applications to deal with text based interfaces
> > like uevent, rather than using netlink to listen for events.
> >
> > Note, this does not deal with network namespaces but that is a generic
> > problem that already exists with kobjects (see rename events).
> >
> > Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
> >
> > ---
> >  net/core/Makefile |    1
> >  net/core/uevent.c |   61 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >  2 files changed, 62 insertions(+)
> >
> > --- a/net/core/Makefile 2008-11-24 08:40:10.000000000 -0800
> > +++ b/net/core/Makefile 2008-11-24 08:51:01.000000000 -0800
> > @@ -17,3 +17,4 @@ obj-$(CONFIG_NET_PKTGEN) += pktgen.o
> >  obj-$(CONFIG_NETPOLL) += netpoll.o
> >  obj-$(CONFIG_NET_DMA) += user_dma.o
> >  obj-$(CONFIG_FIB_RULES) += fib_rules.o
> > +obj-$(CONFIG_HOTPLUG) += uevent.o
> > --- /dev/null   1970-01-01 00:00:00.000000000 +0000
> > +++ b/net/core/uevent.c 2008-11-24 09:06:50.000000000 -0800
> > @@ -0,0 +1,60 @@
> > +/*
> > + * Linux network device event notification
> > + *
> > + * Author:
> > + *     Stephen Hemminger <shemminger@vyatta.com>
> > + */
> > +
> > +#include <linux/kernel.h>
> > +#include <linux/netdevice.h>
> > +#include <linux/kobject.h>
> > +#include <linux/notifier.h>
> > +
> > +/*
> > + * Generate uevent in response to nework device changes.
> > + * NB: KOBJ_MOVE is already genereated by kobject_rename
> > + */
> > +static int netdev_event(struct notifier_block *this, unsigned long event, void *ptr)
> > +{
> > +       struct net_device *netdev = ptr;
> > +
> > +       switch (event) {
> > +       case NETDEV_UNREGISTER:
> > +               kobject_uevent(&netdev->dev.kobj, KOBJ_REMOVE);
> > +               break;
> > +       case NETDEV_REGISTER:
> > +               kobject_uevent(&netdev->dev.kobj, KOBJ_ADD);
> > +               break;
> 
> Did you do anything else to prevent the duplicated add/remove events?
> The core does send these already. I replied with a "udevadm monitor"
> output to your earlier mail. Don't you see the duplicates on your box?
> 
> Thanks,
> Kay

okay, then i'll just take it out of here.

  reply	other threads:[~2008-11-24 20:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-22  7:41 [RFC] network devices generating uevents? Stephen Hemminger
2008-11-22 14:08 ` Kay Sievers
2008-11-22 19:22 ` Karl O. Pinc
2008-11-23  2:13 ` Marcel Holtmann
2008-11-23  6:32 ` Stephen Hemminger
2008-11-23 16:13 ` Kay Sievers
2008-11-24 19:45   ` [PATCH] netdev: generate kobject uevent on network events Stephen Hemminger
2008-11-24 19:55     ` Kay Sievers
2008-11-24 20:06       ` Stephen Hemminger [this message]
2008-11-25  8:39         ` David Miller
2008-11-24 20:06     ` Ben Hutchings
2008-11-24 23:03       ` [PATCH] netdev: generate kobject uevent on network state Stephen Hemminger
2008-11-25  3:08         ` [PATCH] netdev: generate kobject uevent on network state transitions Kay Sievers
2008-11-25  3:51         ` Marcel Holtmann
2008-11-25  4:14           ` [PATCH] netdev: generate kobject uevent on network state Stephen Hemminger
2008-11-25  9:09             ` David Miller
2008-11-26  5:24               ` [PATCH] netdev: generate kobject uevent on network state transitions Marcel Holtmann
2008-11-26 12:09                 ` Kay Sievers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081124120645.417ea6e7@extreme \
    --to=shemminger@vyatta.com \
    --cc=davem@davemloft.net \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).