From: Eric Dumazet <eric.dumazet@gmail.com>
To: Krishna Kumar <krkumar2@in.ibm.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH] net: Handle NETREG_UNINITIALIZED devices correctly
Date: Wed, 09 Dec 2009 10:57:44 +0100 [thread overview]
Message-ID: <4B1F7498.2090007@gmail.com> (raw)
In-Reply-To: <20091209082602.19053.97297.sendpatchset@localhost.localdomain>
Krishna Kumar a écrit :
> From: Krishna Kumar <krkumar2@in.ibm.com>
>
> Fix two problems:
>
> 1. If unregister_netdevice_many() is called with both registered
> and unregistered devices, rollback_registered_many() bails out
> when it reaches the first unregistered device. The processing
> of the prior registered devices is unfinished, and the
> remaining devices are skipped, and possible registered netdev's
> are leaked/unregistered.
>
> 2. System hangs or panics depending on how the devices are passed,
> since when netdev_run_todo() runs, some devices were not fully
> processed.
>
> Tested by passing intermingled unregistered and registered vlan
> devices to unregister_netdevice_many() as follows:
> 1. dev, fake_dev1, fake_dev2: hangs in run_todo
> ("unregister_netdevice: waiting for eth1.100 to become
> free. Usage count = 1")
> 2. fake_dev1, dev, fake_dev2: failure during de-registration
> and next registration, followed by a vlan driver Oops
> during subsequent registration.
>
> Confirmed that the patch fixes both cases.
>
> Signed-off-by: Krishna Kumar <krkumar2@in.ibm.com>
Acked-by: Eric Dumazet <eric.dumazet@gmail.com>
Thanks !
next prev parent reply other threads:[~2009-12-09 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 8:26 [PATCH] net: Handle NETREG_UNINITIALIZED devices correctly Krishna Kumar
2009-12-09 9:57 ` Eric Dumazet [this message]
2009-12-11 23:12 ` David Miller
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=4B1F7498.2090007@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=krkumar2@in.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;
as well as URLs for NNTP newsgroup(s).