mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux1394-devel@lists.sourceforge.net,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-kernel@vger.kernel.org,
	Dmitry Torokhov <dtor@insightbb.com>
Subject: Re: [PATCH] ieee1394: nodemgr: fix deadlock in shutdown
Date: Wed, 22 Nov 2006 21:09:42 +0100	[thread overview]
Message-ID: <4564AE86.2020905@s5r6.in-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0611212028160.5677-100000@netrider.rowland.org>

Alan Stern wrote:
> On Tue, 21 Nov 2006, Stefan Richter wrote:
>> There is now a /sys/bus/ieee1394/drivers/ieee1394,

(I'll rename it to nodemgr when I commit this patch.)

>> whose "bind" and "unbind" attributes are not welcome.  Is there a way
>> to disable them?
> 
> You can always prevent "bind" from operating by returning an error code
> from the driver's probe routine (although it's not clear why you would
> want to do that).  I don't think there's any way to make the "unbind"
> attribute stop working.
> 
> You could violate the layering and remove the attribute files directly.  
> But that would be a race; there would remain a brief interval between the 
> time the files were created and the time you removed them.

Does this matter if there is no device which can be unbound?

Anyway, I don't think I will go this route unless a real problem with
the attributes turns up.

> Lastly, you could remove source of your deadlock by having the unbind 
> routine for the new driver delete all the child device structures.

Hmm, I won't believe you until I actually try it. :-)

> In fact, just to make things more symmetric and logical you could have 
> the probe routine create those child devices in the first place!

Sounds good. It's on my .plan now.
-- 
Stefan Richter
-=====-=-==- =-== =-==-
http://arcgraph.de/sr/

  reply	other threads:[~2006-11-22 20:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19  0:12 deadlock in "modprobe -r ohci1394" shortly after "modprobe ohci1394" Stefan Richter
2006-11-19 14:23 ` Stefan Richter
2006-11-19 19:54   ` Alan Stern
2006-11-19 21:55     ` Stefan Richter
2006-11-20 19:31       ` Alan Stern
2006-11-20 20:45         ` Stefan Richter
2006-11-20 21:28           ` Alan Stern
2006-11-21  0:21             ` Stefan Richter
2006-11-21  0:49               ` Alan Stern
2006-11-21  8:05                 ` Stefan Richter
2006-11-21 21:50                   ` [PATCH] ieee1394: nodemgr: fix deadlock in shutdown Stefan Richter
2006-11-22  2:02                     ` Alan Stern
2006-11-22 20:09                       ` Stefan Richter [this message]
2006-11-20  3:41     ` deadlock in "modprobe -r ohci1394" shortly after "modprobe ohci1394" Dmitry Torokhov
2006-11-20 19:18       ` Alan Stern

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=4564AE86.2020905@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=dtor@insightbb.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --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®