From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 602] New: warnings on hcd rmmod: "dangling refs(N) to bus B" (fwd)
Date: Fri, 18 Apr 2003 13:49:05 -0700 [thread overview]
Message-ID: <1382940000.1050698945@flay> (raw)
http://bugme.osdl.org/show_bug.cgi?id=602
Summary: warnings on hcd rmmod: "dangling refs(N) to bus B"
Kernel Version: 2.5.66
Status: NEW
Severity: low
Owner: greg@kroah.com
Submitter: dbrownell@users.sourceforge.net
The bus refcounting mechanism is broken, it often produces warning messages like that one when modules are removed. The problem appears to be an extremely long-standing one, at least in terms of the how-to-reproduce I saw: - connect a device that won't immediately enumerate, so that setting its address needs to be retried (or similar error, like set_configuration failing) - unplug that device ... at this point the refcount is wrong, but you can't tell until - rmmod the relevant HCD. This particular cause of that message is because the bus refcount isn't released on error. The fix isn't as straightforward as it should be because of funky calling conventions ("longstanding", likely since 2.4), but it's not
complicated either.
reply other threads:[~2003-04-18 20:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1382940000.1050698945@flay \
--to=mbligh@aracnet.com \
--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