Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: netdev@vger.kernel.org, kaber@trash.net
Subject: Re: [PATCH 4/6] [NET]: Allow netdev REGISTER/CHANGENAME events to fail
Date: Mon, 30 Jul 2007 17:03:57 -0700 (PDT)	[thread overview]
Message-ID: <20070730.170357.44097637.davem@davemloft.net> (raw)
In-Reply-To: <E1IDzLk-0000AI-00@gondolin.me.apana.org.au>

From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Thu, 26 Jul 2007 17:09:36 +0800

> [NET]: Allow netdev REGISTER/CHANGENAME events to fail
> 
> This patch adds code to allow errors to be passed up from event
> handlers of NETDEV_REGISTER and NETDEV_CHANGENAME.  It also adds
> the notifier_from_errno/notifier_to_errnor helpers to pass the
> errno value up to the notifier caller.
> 
> If an error is detected when a device is registered, it causes
> that operation to fail.  A NETDEV_UNREGISTER will be sent to
> all event handlers.
> 
> Similarly if NETDEV_CHANGENAME fails the original name is restored
> and a new NETDEV_CHANGENAME event is sent.
> 
> As such all event handlers must be idempotent with respect to
> these events.
> 
> When an event handler is registered NETDEV_REGISTER events are
> sent for all devices currently registered.  Should any of them
> fail, we will send NETDEV_GOING_DOWN/NETDEV_DOWN/NETDEV_UNREGISTER
> events to that handler for the devices which have already been
> registered with it.  The handler registration itself will fail.
> 
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

Applied.

Interesting encoding scheme :-)

  reply	other threads:[~2007-07-31  0:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26  9:07 [0/6] Allow registration/change name notifications to fail Herbert Xu
2007-07-26  9:09 ` [PATCH 1/6] [NET]: Call uninit if necessary in register_netdevice Herbert Xu
2007-07-30 23:29   ` David Miller
2007-07-26  9:09 ` [PATCH 2/6] [NET]: Take dev_base_lock when moving device name hash list entry Herbert Xu
2007-07-30 23:36   ` David Miller
2007-07-26  9:09 ` [PATCH 3/6] [NET] loopback: Panic if registration fails Herbert Xu
2007-07-30 23:38   ` David Miller
2007-07-26  9:09 ` [PATCH 4/6] [NET]: Allow netdev REGISTER/CHANGENAME events to fail Herbert Xu
2007-07-31  0:03   ` David Miller [this message]
2007-07-26  9:09 ` [PATCH 5/6] [IPV4/IPV6]: Fail registration if inet device construction fails Herbert Xu
2007-07-31  0:05   ` David Miller
2007-07-26  9:09 ` [PATCH 6/6] [IPV6]: Remove circular dependency on if_inet6.h Herbert Xu
2007-07-31  0:06   ` David Miller
2007-07-26 10:37 ` [0/6] Allow registration/change name notifications to fail Stephen Hemminger
2007-07-26 11:03   ` Herbert Xu

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=20070730.170357.44097637.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kaber@trash.net \
    --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