From: "Leonardo Chiquitto" <lchiquitto@novell.com>
To: "Alan Stern" <stern@rowland.harvard.edu>,
"Jiri Kosina" <jkosina@suse.cz>
Cc: "Greg KH" <greg@kroah.com>, "Oliver Neukum" <oliver@neukum.org>,
<linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] USB: fix deadlock in HCD code
Date: Wed, 21 May 2008 13:32:10 -0600 [thread overview]
Message-ID: <48344E8A.7E42.0086.0@novell.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0805211042070.2490-100000@iolanthe.rowland.org>
>> > > Used in the suspend code. Your patch is indeed correct, but I fear
>> > > there might be a second bug caused by wrong calling conditions.
>> > The problem in the Novell bugzilla entry was caused by the fact that the
>> > OHCI irq routine was invoked with interrupts enabled, owing to a missing
>> > IRQF_DISABLED flag. That bug has already been fixed in 2.6.25.
>>
>> That indeed is 2.6.25 kernel. I guess you are talking about commit
>> 442258e2ff69 here.
>
> Yes.
>
>> If so, the reporter is definitely using the kernel
>> containing this commit, and the lockups still trigger.
>>
>> Seems that my patch is papering over the real bug (someone enabling
>> interrupts somewhere) indeed, but I can't seem to be able to find such
>> codepath.
>
> You could try testing the interrupt-enable flag at various places
> in ohci-hcd (start with finish_urb) and printing an error message if
> interrupts are enabled.
>
> One possibility is that in an earlier call to finish_urb,
> usb_hcd_giveback_urb was called with interrupts disabled and returned
> with interrupts enabled. In other words, some driver's callback
> routine may have enabled interrupts incorrectly.
Alan,
I am trying your suggestion right now. Lets see if it finds something.
Thanks,
Leonardo
next prev parent reply other threads:[~2008-05-21 19:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 12:09 [PATCH] USB: fix deadlock in HCD code Jiri Kosina
2008-05-21 13:21 ` Oliver Neukum
2008-05-21 13:27 ` Jiri Kosina
2008-05-21 13:32 ` Oliver Neukum
2008-05-21 13:36 ` Jiri Kosina
2008-05-21 13:47 ` Oliver Neukum
2008-05-21 14:13 ` Alan Stern
2008-05-21 14:22 ` Jiri Kosina
2008-05-21 14:46 ` Alan Stern
2008-05-21 19:32 ` Leonardo Chiquitto [this message]
2008-05-21 20:03 ` Oliver Neukum
2008-05-21 14:29 ` David Vrabel
2008-05-21 14:42 ` Alan Stern
2008-05-21 14:53 ` David Vrabel
2008-05-21 14:58 ` Alan Stern
2008-05-21 14:31 ` Oliver Neukum
2008-05-21 13:40 ` Oliver Neukum
2008-05-21 22:26 ` Peter Zijlstra
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=48344E8A.7E42.0086.0@novell.com \
--to=lchiquitto@novell.com \
--cc=greg@kroah.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=stern@rowland.harvard.edu \
/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