mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.name>
To: "John Tyner" <jtyner@cs.ucr.edu>, "Greg KH" <greg@kroah.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Vicam/3com homeconnect usb camera driver
Date: Sun, 6 Oct 2002 23:44:02 +0200	[thread overview]
Message-ID: <m17yJwe-006imWC@Mail.ZEDAT.FU-Berlin.DE> (raw)
In-Reply-To: <000c01c26d7f$e3a068d0$0a00a8c0@refresco>

On Sunday 06 October 2002 23:32, John Tyner wrote:
> > And you should probably kill the tasklet before you unregister the video
> > device.
>
> The more I think about this, the more I think that killing the tasklet
> after unregistering the device is the correct way.
>
> From what I can tell, there are two ways that the disconnect function can
> be called: a physical disconnect or a module removal.

And as a result of an ioctl() through usbfs.

> In the case of a physical disconnect, the ordering probably doesn't matter
> because the tasklet won't be scheduled again because urb's would fail to
> complete successfully.
>
> The case of module removal becomes a bit more complicated (for reasons
> concerning module unload races that are being discussed by people far
> smarter than I). But in any event, I think that it makes more sense to
> unregister the open/close/etc. interface so that there is less chance of
> trying to send another urb (thus causing another schedule of the tasklet)
> before actually killing the tasklet.
>
> This also brings up the (somewhat) rhetorical question I posed in the
> driver's disconnect function. What happens when a disconnect occurs while
> the device is open?

I can't tell right now. I'll sync up after returning home and look into the 
matter.

	Regards
		Oliver

  reply	other threads:[~2002-10-06 22:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-06 21:32 John Tyner
2002-10-06 21:44 ` Oliver Neukum [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-06  2:58 John Tyner
2002-10-06 10:11 ` Oliver Neukum
2002-10-06 17:35   ` John Tyner
2002-10-06 22:01     ` Oliver Neukum
2002-10-06 23:25       ` John Tyner
2002-10-07  4:55         ` Oliver Neukum
2002-10-07  9:43         ` Oliver Neukum
2002-10-07 21:51           ` John Tyner
2002-10-04  3:59 John Tyner
2002-10-04  4:50 ` Greg KH
2002-10-04  5:05   ` John Tyner
2002-10-04  5:22     ` Greg KH
2002-10-06  2:57   ` John Tyner
2002-10-06 21:06 ` Pavel Machek
2002-10-07 18:43   ` John Tyner

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=m17yJwe-006imWC@Mail.ZEDAT.FU-Berlin.DE \
    --to=oliver@neukum.name \
    --cc=greg@kroah.com \
    --cc=jtyner@cs.ucr.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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®