From: Andrew Morton <akpm@linux-foundation.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: netdev@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@kernel-bugs.osdl.org>,
Paul Mackerras <paulus@samba.org>,
kernelbugs@tecnopolis.ca
Subject: Re: [Bugme-new] [Bug 8638] New: unregister_netdevice: waiting for ppp0 to become free. pppoe + multihome + htb qos?
Date: Mon, 18 Jun 2007 08:23:31 -0700 [thread overview]
Message-ID: <20070618082331.d1b7fd93.akpm@linux-foundation.org> (raw)
In-Reply-To: <46769D06.3050603@redhat.com>
On Mon, 18 Jun 2007 10:56:06 -0400 Chuck Ebbert <cebbert@redhat.com> wrote:
>
> Is there any way to print the addresses the notifier is calling
> to try and release net device references? I see:
>
> net/core/dev/c::netdev_wait_allrefs():
>
> while (atomic_read(&dev->refcnt) != 0) {
> if (time_after(jiffies, rebroadcast_time + 1 * HZ)) {
> rtnl_lock();
>
> /* Rebroadcast unregister notification */
> raw_notifier_call_chain(&netdev_chain,
> NETDEV_UNREGISTER, dev);
>
> but don't see any way to print the functions that get called.
Nope. I guess we could add some print_notifier_call_chain() thing, but
then we'd need one flavour per locking scheme and it would get ridiculous.
I guess just an unlocked version would be OK - it's just a debug thing.
prev parent reply other threads:[~2007-06-18 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8638-10286@http.bugzilla.kernel.org/>
2007-06-16 15:34 ` [Bugme-new] [Bug 8638] New: unregister_netdevice: waiting for ppp0 to become free. pppoe + multihome + htb qos? Andrew Morton
2007-06-18 14:56 ` Chuck Ebbert
2007-06-18 15:18 ` Stephen Hemminger
2007-06-18 15:23 ` Andrew Morton [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=20070618082331.d1b7fd93.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@kernel-bugs.osdl.org \
--cc=cebbert@redhat.com \
--cc=kernelbugs@tecnopolis.ca \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.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).