From: Greg KH <gregkh@suse.de>
To: Eric Lescouet <eric.lescouet@vlx.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"usbip-devel@lists.sourceforge.net"
<usbip-devel@lists.sourceforge.net>
Subject: Re: [PATCH]: Fix deadlock in USBIP driver (staging), linux-2.6.34-rc5
Date: Thu, 22 Apr 2010 10:02:07 -0700 [thread overview]
Message-ID: <20100422170207.GA18830@suse.de> (raw)
In-Reply-To: <4BD07F2A.8080808@VirtualLogix.com>
On Thu, Apr 22, 2010 at 06:54:02PM +0200, Eric Lescouet wrote:
> Hi,
> When detaching a port from the client side (usbip --detach 0),
> the event thread, on the server side, is going to deadlock.
> The "eh" server thread is getting USBIP_EH_RESET event and calls:
> -> stub_device_reset() -> usb_reset_device()
> the USB framework is then calling back _in the same "eh" thread_ :
> -> stub_disconnect() -> usbip_stop_eh() -> wait_for_completion()
> the "eh" thread is being asleep forever, waiting for its own completion.
> The patch checks if "eh" is the current thread, in usbip_stop_eh().
Ok, but does the lock_kernel() call you just made actually prevent this
from happening? Isn't there some other lock you can use instead?
> Please Cc me in reply, I'm not in the list.
Also, to have patches that we can apply, we need a "Signed-off-by:"
line. See the file, Documentation/SubmittingPatches for what this
means.
>
> b.r.
>
> ------------------
>
> diff -Nur linux-2.6.34-rc5/drivers/staging/usbip/usbip_event.c
> linux-2.6.34-rc5.new/drivers/staging/usbip/usbip_event.c
> --- linux-2.6.34-rc5/drivers/staging/usbip/usbip_event.c
> 2010-04-20 01:29:56.000000000 +0200
Your email client wrapped the patch and made it unappliable :(
thanks,
greg k-h
next prev parent reply other threads:[~2010-04-22 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 16:54 [PATCH]: Fix deadlock in USBIP driver (staging), linux-2.6.34-rc5 Eric Lescouet
2010-04-22 17:02 ` Greg KH [this message]
2010-04-22 18:12 ` Eric Lescouet
2010-04-22 18:51 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-04-22 22:10 Eric Lescouet
2010-04-24 0:55 Eric Lescouet
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=20100422170207.GA18830@suse.de \
--to=gregkh@suse.de \
--cc=eric.lescouet@vlx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=usbip-devel@lists.sourceforge.net \
/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).