From: David Miller <davem@davemloft.net>
To: kernel@nn7.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 24rc8: unregister_netdevice: waiting for ... to become free. Usage count = 1?
Date: Tue, 22 Jan 2008 22:44:42 -0800 (PST) [thread overview]
Message-ID: <20080122.224442.142676954.davem@davemloft.net> (raw)
In-Reply-To: <1201070541.22958.53.camel@localhost>
From: Soeren Sonnenburg <kernel@nn7.de>
Date: Wed, 23 Jan 2008 07:42:21 +0100
> Dear all,
>
> since some 2.6.24rc version I suddenly experience such messages on
> console when trying to shutdown a vpn connection:
>
> unregister_netdevice: waiting for tun0 to become free. Usage count = 1
>
> or when removing an usb wlan dongle (although it was ifconfig wlan0
> down'd before)
Current GIT already has a fix for this, attached below:
[NEIGH]: Revert 'Fix race between neigh_parms_release and neightbl_fill_parms'
Commit 9cd40029423701c376391da59d2c6469672b4bed (Fix race between
neigh_parms_release and neightbl_fill_parms) introduced device
reference counting regressions for several people, see:
http://bugzilla.kernel.org/show_bug.cgi?id=9778
for example.
Signed-off-by: David S. Miller <davem@davemloft.net>
diff --git a/net/core/neighbour.c b/net/core/neighbour.c
index cc8a2f1..29b8ee4 100644
--- a/net/core/neighbour.c
+++ b/net/core/neighbour.c
@@ -1316,6 +1316,8 @@ void neigh_parms_release(struct neigh_table *tbl, struct neigh_parms *parms)
*p = parms->next;
parms->dead = 1;
write_unlock_bh(&tbl->lock);
+ if (parms->dev)
+ dev_put(parms->dev);
call_rcu(&parms->rcu_head, neigh_rcu_free_parms);
return;
}
@@ -1326,8 +1328,6 @@ void neigh_parms_release(struct neigh_table *tbl, struct neigh_parms *parms)
void neigh_parms_destroy(struct neigh_parms *parms)
{
- if (parms->dev)
- dev_put(parms->dev);
kfree(parms);
}
next prev parent reply other threads:[~2008-01-23 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 6:42 Soeren Sonnenburg
2008-01-23 6:44 ` David Miller [this message]
2008-01-23 7:49 ` Soeren Sonnenburg
2008-01-29 8:59 ` Soeren Sonnenburg
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=20080122.224442.142676954.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kernel@nn7.de \
--cc=linux-kernel@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
Powered by JetHome