From: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
To: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Neil Jones <neiljay-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Fwd: usbnet: Recursive Locking bug ?
Date: Tue, 7 Dec 2010 20:55:50 -0800 (PST) [thread overview]
Message-ID: <917120.68161.qm@web180301.mail.gq1.yahoo.com> (raw)
In-Reply-To: <AANLkTi=VB0Kt=2c1C1b-Ps8x_zA5Tnf+tfHjvO8gWgm8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
I'll look at this some later, though I seem to
have missed a post with the diagnostic saying
what lock is being recursed.
That particular chunk of code has periodically
turned up problems, and isn't very pretty. But
the most curious aspect of it is that it seemed
to shake out HCD-specific behaviors. (We've
gotten rid of most such code by now, this is a
slight exception.
Specifically, HCDs that could unlink speedily
without certain locking patterns (ISTR OHCI and
EHCI, if not also UHCI) didn't trigger oddness.
But some other HCDs, with different approaches
to unlinking URBs, were less happy. ( I was
likely working with MUSB at the time.)
I spent some time trying to rework that code in
"usbnet", but no clean-and-obvious solutions
became apparent when I did that (a few years
back). Plus, ISTR being the only person to
find issues (back then), so I couldn't make
an argument to spend much more time on it.
Hope that helps anyone trying to fix this.
- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-12-08 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 14:08 usbnet: Recursive Locking bug ? Neil Jones
[not found] ` <AANLkTikBjxZEvWu+322qP2v0MU9xFQrgJmq2xA-Zdo32-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-07 14:54 ` Oliver Neukum
[not found] ` <AANLkTi=Dzc37qxXC0oK48pnuWss9gHJE3ARDEUGfi7QA@mail.gmail.com>
2010-12-07 16:15 ` Fwd: " Neil Jones
2010-12-07 16:46 ` Alan Stern
[not found] ` <AANLkTi=VB0Kt=2c1C1b-Ps8x_zA5Tnf+tfHjvO8gWgm8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-08 4:55 ` David Brownell [this message]
[not found] ` <917120.68161.qm-g47maUHHHF+ORdMXk8NaZPu2YVrzzGjVVpNB7YpNyf8@public.gmane.org>
2010-12-08 9:58 ` Neil Jones
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=917120.68161.qm@web180301.mail.gq1.yahoo.com \
--to=david-b-ybekhbn/0ldr7s880joybq@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=neiljay-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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