public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arne Caspari <arne@datafloater.de>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/base/driver.c : driver_unregister
Date: Sat, 11 Dec 2004 20:24:01 +0100	[thread overview]
Message-ID: <41BB4951.2080304@datafloater.de> (raw)
In-Reply-To: <20041211191113.A13985@flint.arm.linux.org.uk>

Russell King wrote:

>On Sat, Dec 11, 2004 at 07:54:32PM +0100, Arne Caspari wrote:
>  
>
>>I think the meaning of this patch is obvious: In driver_unregister, the 
>>bus_remove_driver function call was called outside the driver unload 
>>semaphore which should obviously protect it.
>>    
>>
>
>No.  The semaphore is there to ensure that the function does not
>return until the driver structure has a use count of zero.  If you
>tested your patch, you'd find that your change would deadlock on
>the locked semaphore.
>  
>

Russell,

Ah, now I understand that thing.  Reading the comments again, I should 
have seen the reason for this earlier.

I am sorry I can not test that patch since unloading of the modules I am 
currently testing blocks anyway. This makes it very hard to test the 
patch :-( and currently this was the reason why I was going to this.

Sorry if I caused any inconvenience.

 /Arne



  reply	other threads:[~2004-12-11 21:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-11 18:54 [PATCH] drivers/base/driver.c : driver_unregister Arne Caspari
2004-12-11 19:11 ` Russell King
2004-12-11 19:24   ` Arne Caspari [this message]
2004-12-13  7:21     ` Arne Caspari
2004-12-13 21:07       ` Matt Mackall

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=41BB4951.2080304@datafloater.de \
    --to=arne@datafloater.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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