From: Stephen Hemminger <shemminger@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: dlezcano@fr.ibm.com, netdev@vger.kernel.org
Subject: Re: [patch 1/1][CORE] resend - fix free_netdev on register_netdev failure
Date: Tue, 30 Oct 2007 21:52:43 -0700 [thread overview]
Message-ID: <20071030215243.60e276bf@freepuppy.rosehill> (raw)
In-Reply-To: <20071030.153830.120597346.davem@davemloft.net>
On Tue, 30 Oct 2007 15:38:30 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Daniel Lezcano <dlezcano@fr.ibm.com>
> Date: Tue, 30 Oct 2007 17:19:26 +0100
>
> > Point 1:
> > The unregistering of a network device schedule a netdev_run_todo.
> > This function calls dev->destructor when it is set and the
> > destructor calls free_netdev.
> >
> > Point 2:
> > In the case of an initialization of a network device the usual code
> > is:
> > * alloc_netdev
> > * register_netdev
> > -> if this one fails, call free_netdev and exit with error.
> >
> > Point 3:
> > In the register_netdevice function at the later state, when the device
> > is at the registered state, a call to the netdevice_notifiers is made.
> > If one of the notification falls into an error, a rollback to the
> > registered state is done using unregister_netdevice.
> >
> > Conclusion:
> > When a network device fails to register during initialization because
> > one network subsystem returned an error during a notification call
> > chain, the network device is freed twice because of fact 1 and fact 2.
> > The second free_netdev will be done with an invalid pointer.
> >
> > Proposed solution:
> > The following patch move all the code of unregister_netdevice *except*
> > the call to net_set_todo, to a new function "rollback_registered".
> >
> > The following functions are changed in this way:
> > * register_netdevice: calls rollback_registered when a notification fails
> > * unregister_netdevice: calls rollback_register + net_set_todo, the call
> > order to net_set_todo is changed because it is the
> > latest now. Since it justs add an element to a list
> > that should not break anything.
> >
> > Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>
>
> Looks good, applied.
Agreed, but I wish the unwind code wouldn't have to be separate function.
--
Stephen Hemminger <shemminger@linux-foundation.org>
prev parent reply other threads:[~2007-10-31 4:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071030161925.487151276@mai.toulouse-stg.fr.ibm.com>
2007-10-30 16:19 ` [patch 1/1][CORE] resend - fix free_netdev on register_netdev failure Daniel Lezcano
2007-10-30 22:38 ` David Miller
2007-10-31 4:52 ` Stephen Hemminger [this message]
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=20071030215243.60e276bf@freepuppy.rosehill \
--to=shemminger@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dlezcano@fr.ibm.com \
--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