mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Lescouet <Eric.Lescouet@VirtualLogix.com>
To: Greg KH <gregkh@suse.de>
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 20:12:05 +0200	[thread overview]
Message-ID: <4BD09175.9030703@VirtualLogix.com> (raw)
In-Reply-To: <20100422170207.GA18830@suse.de>

Greg KH wrote:
[...]
> 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?
> 

Right. lock_kernel() is not needed (was copy/paste).
The deadlock is avoided by not calling wait_for_completion()
when the code is executed by the "eh" thread itself.

> Also, to have patches that we can apply, we need a "Signed-off-by:"
> line.  See the file, Documentation/SubmittingPatches for what this
> means.

Understood.

> Your email client wrapped the patch and made it unappliable :(
> 
> thanks,
> 
> greg k-h

Sorry about that. Please find below an hopefully better one.
Thanks,
	Eric.


Signed-off-by: Eric Lescouet <eric@lescouet.org>
-------------

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                                       
+++ linux-2.6.34-rc5.new/drivers/staging/usbip/usbip_event.c    2010-04-22 19:19:52.997889126 +0200                                       
@@ -117,6 +117,9 @@
 {                                                                                                                                        
        struct usbip_task *eh = &ud->eh;                                                                                                  
                                                                                                                                          
+       if (eh->thread == current)                                                                                                        
+               return; /* do not wait for myself */                                                                                      
+                                                                                                                                         
        wait_for_completion(&eh->thread_done);                                                                                            
        usbip_dbg_eh("usbip_eh has finished\n");                                                                                          
 }                                                                                                                                        


  reply	other threads:[~2010-04-22 18:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 16:54 Eric Lescouet
2010-04-22 17:02 ` Greg KH
2010-04-22 18:12   ` Eric Lescouet [this message]
2010-04-22 18:51     ` Greg KH
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=4BD09175.9030703@VirtualLogix.com \
    --to=eric.lescouet@virtuallogix.com \
    --cc=gregkh@suse.de \
    --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

Powered by JetHome