public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>,
	mat@mut38-1-82-67-62-65.fbx.proxad.net,
	matthieu castet <castet.matthieu@free.fr>
Subject: Re: device_remove_file and disconnect
Date: Sat, 2 Jul 2005 23:38:29 -0500	[thread overview]
Message-ID: <200507022338.30806.dtor_core@ameritech.net> (raw)
In-Reply-To: <20050630170406.GA11334@kroah.com>

On Thursday 30 June 2005 12:04, Greg KH wrote:
> Hm, in thinking about it, it might make more sense to rework the usb
> core to handle this better.  Possibly add a release() callback to the
> driver when the device is actually being freed.  Wouldn't be that hard
> to do so, and might cut down on some of the common locking errors.
> 

I amafraid this will not help in this particular case - the problem is
with driver-specific memory which is freed way before device disappears.
Consider unloading aiptek module - we need to free aiptek structure when
we unbinding driver but corrsponding USB device will stay there (fully
fucntional with its 'struct device' not going anywhere) until you
physically pull tablet's cord out.

-- 
Dmitry

      parent reply	other threads:[~2005-07-03  4:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 16:59 device_remove_file and disconnect matthieu castet
2005-06-29 18:46 ` Greg KH
2005-06-29 20:17   ` matthieu castet
2005-06-29 22:42     ` Greg KH
2005-06-30  7:26       ` mat
2005-06-30 17:04         ` Greg KH
2005-06-30 20:31           ` matthieu castet
2005-07-02 23:27             ` matthieu castet
2005-07-03  4:54               ` Dmitry Torokhov
2005-07-25  1:54             ` Greg KH
2005-06-30 20:36           ` Dmitry Torokhov
2005-07-03  4:38           ` Dmitry Torokhov [this message]

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=200507022338.30806.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=castet.matthieu@free.fr \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mat@mut38-1-82-67-62-65.fbx.proxad.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