From: David Brownell <david-b@pacbell.net>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-usb-devel@lists.sourceforge.net,
Harald Welte <laforge@gnumonks.org>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [BUG] oops while completing async USB via usbdevio
Date: Mon, 30 May 2005 16:12:07 -0700 [thread overview]
Message-ID: <200505301612.07850.david-b@pacbell.net> (raw)
In-Reply-To: <200505310109.06445.oliver@neukum.org>
On Monday 30 May 2005 4:09 pm, Oliver Neukum wrote:
> Am Dienstag, 31. Mai 2005 00:55 schrieb David Brownell:
> > The logic closing an open usbfs file -- which is done before any task
> > exits with such an open file -- is supposed to block till all its URBs
> > complete. So the pointer to the task "should" be valid for as long as
> > any URB it's submitted is active.
>
> What happens if you pass such an fd through a socket?
Why I suppose then you might find glitches in the design underlying
the usbfs code. I put "should" in scare-quotes for a reason.
next prev parent reply other threads:[~2005-05-30 23:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 19:44 [BUG] oops while completing async USB via usbdevio Harald Welte
2005-05-30 21:26 ` Harald Welte
2005-05-30 22:55 ` [linux-usb-devel] " David Brownell
2005-05-30 23:09 ` Oliver Neukum
2005-05-30 23:12 ` David Brownell [this message]
2005-05-31 8:04 ` Harald Welte
2005-05-31 8:48 ` Harald Welte
2005-05-31 11:45 ` Oliver Neukum
2005-05-31 18:53 ` David Brownell
2005-05-31 22:12 ` Harald Welte
2005-06-06 16:05 ` Harald Welte
2005-06-06 16:24 ` Alan Stern
2005-06-06 16:50 ` Harald Welte
2005-05-30 23:07 ` Oliver Neukum
2005-05-31 8:06 ` Harald Welte
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=200505301612.07850.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oliver@neukum.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.