From: Stefani Seibold <stefani@seibold.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, oneukum@suse.de,
alan@lxorguk.ukuu.org.uk, linux-usb@vger.kernel.org
Subject: Re: [PATCH 04/11] remove usb_interface pointer
Date: Thu, 07 Jun 2012 21:50:21 +0200 [thread overview]
Message-ID: <1339098621.13885.13.camel@wall-e> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1206071118310.1185-100000@iolanthe.rowland.org>
Am Donnerstag, den 07.06.2012, 11:27 -0400 schrieb Alan Stern:
> On Thu, 7 Jun 2012, Stefani Seibold wrote:
> > I think it will be needed, since usb core will decrement the reference
> > when the device go away.
>
> But before it decrements the reference, it will unbind the driver. As
> long as usb-skeleton is careful not to access the device or the
> interface after the disconnect routine returns, it doesn't need to keep
> a reference.
>
> > Lock every access to the usb core if a tedious
> > thing and will waste a lot of code.
>
> With proper design, it's not necessary to lock every access.
> >
> > BTW: An interface have no reference count.
>
> Sure it does. Look at the definitions of usb_get_intf() and
> usb_put_intf() in drivers/usb/core/usb.c.
>
That what i am looking for. If we do an usb_get_intf() in the
skel_probe() function and an usb_put_intf() in skel_delete() function at
the end, then it should be save to access the usb_device pointer by
interface_to_usbdev() in the skel_delete() function. Right?
Greetings,
Stefani
next prev parent reply other threads:[~2012-06-07 19:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 16:27 [PATCH] fix usb skeleton driver stefani
2012-06-06 16:27 ` [PATCH 01/11] fix wrong label in skel_open stefani
2012-06-06 18:52 ` Oliver Neukum
2012-06-06 19:59 ` Stefani Seibold
2012-06-06 16:27 ` [PATCH 02/11] code cleanup stefani
2012-06-06 18:57 ` Oliver Neukum
2012-06-06 16:27 ` [PATCH 03/11] remove dead code stefani
2012-06-06 16:27 ` [PATCH 04/11] remove usb_interface pointer stefani
2012-06-06 18:59 ` Oliver Neukum
2012-06-06 20:04 ` Stefani Seibold
2012-06-06 20:19 ` Alan Stern
2012-06-06 22:54 ` Greg KH
2012-06-07 8:07 ` Stefani Seibold
2012-06-07 11:51 ` Stefani Seibold
2012-06-07 14:28 ` Alan Stern
2012-06-07 15:03 ` Stefani Seibold
2012-06-07 15:27 ` Alan Stern
2012-06-07 19:50 ` Stefani Seibold [this message]
2012-06-07 20:42 ` Alan Stern
2012-06-08 7:18 ` RFC: remove usb_device pointer from usb_skeleton.c Stefani Seibold
2012-06-08 8:28 ` Oliver Neukum
2012-06-08 13:46 ` Alan Stern
2012-06-06 16:27 ` [PATCH 05/11] remove unneeded forward declaration stefani
2012-06-06 16:27 ` [PATCH 06/11] introduce fsync function stefani
2012-06-06 16:27 ` [PATCH 07/11] remove pr_err() noise in skel_open stefani
2012-06-06 16:27 ` [PATCH 08/11] Handle a non blocking read without blocking stefani
2012-06-06 16:27 ` [PATCH 09/11] Synchronize disconnect() handler with open() and release(), to fix races stefani
2012-06-06 16:27 ` [PATCH 10/11] Introduce single user mode stefani
2012-06-06 16:27 ` [PATCH 11/11] Bump version number and add aditional author stefani
2012-06-06 16:55 ` [PATCH] fix usb skeleton driver Alan Stern
2012-06-06 17:53 ` Stefani Seibold
2012-06-06 18:16 ` Alan Stern
2012-06-06 20:19 ` Stefani Seibold
2012-06-06 20:22 ` Alan Stern
2012-06-07 8:13 ` Stefani Seibold
2012-06-07 7:10 ` Bjørn Mork
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=1339098621.13885.13.camel@wall-e \
--to=stefani@seibold.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.de \
--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