mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Oliver Neukum <oliver@neukum.org>
Cc: Greg KH <greg@kroah.com>,
	linux-usb@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>,
	lchiquitto@novell.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: fix deadlock in HCD code
Date: Wed, 21 May 2008 15:36:49 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0805211533500.6718@jikos.suse.cz> (raw)
In-Reply-To: <200805211533.00221.oliver@neukum.org>

On Wed, 21 May 2008, Oliver Neukum wrote:

> This turns out not to be the case. Interrupts are disabled.

You're right, this callchain can't cause the deadlock indeed. I'll go 
through the other possibilities.

To give some background to others reading this thread -- Leonardo (in CC) 
reported [1] that this patch fixes hard kernel hangs he has been seeing 
when using USB CDMA modem.

Still, we don't currently seem to see the place where the interrupts get 
enabled that makes the deadlock to trigger.

[1] https://bugzilla.novell.com/show_bug.cgi?id=378509

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2008-05-21 13:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 12:09 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 [this message]
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
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=Pine.LNX.4.64.0805211533500.6718@jikos.suse.cz \
    --to=jkosina@suse.cz \
    --cc=greg@kroah.com \
    --cc=lchiquitto@novell.com \
    --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

all inboxes | Powered by JetHome®