[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201108050959.00873.oliver@neukum.org>
Date: Fri, 5 Aug 2011 09:59:00 +0200
From: Oliver Neukum <oliver@...kum.org>
To: Hans de Goede <hdegoede@...hat.com>
Cc: Greg KH <greg@...ah.com>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
linux-usb@...r.kernel.org, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org, libusb-devel@...ts.sourceforge.net,
Alexander Graf <agraf@...e.de>,
Gerd Hoffmann <kraxel@...hat.com>, hector@...cansoft.com,
Jan Kiszka <jan.kiszka@...mens.com>,
Stefan Hajnoczi <stefanha@...ux.vnet.ibm.com>,
pbonzini@...hat.com, Anthony Liguori <aliguori@...ibm.com>,
Jes Sorensen <Jes.Sorensen@...hat.com>,
Alan Stern <stern@...land.harvard.edu>,
Felipe Balbi <balbi@...com>,
Clemens Ladisch <clemens@...isch.de>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Theodore Kilgore <kilgota@...ach.math.auburn.edu>,
Adam Baker <linux@...er-net.org.uk>
Subject: Re: USB mini-summit at LinuxCon Vancouveroliver
Am Freitag, 5. August 2011, 09:45:56 schrieb Hans de Goede:
> This is the issue on which I feel a bit stonewalled. Simple putting your
> fingers in your ears and singing la la la do it in userspace is not going
> to cut it here. There is no way to do this race free in userspace, unless
> all possible callers of mount get modified. Moreover 99% of the necessary
> accounting for this is already done in the kernel. We already have the notion
> of a block device being in use. We simply need to add some code to pass
> this notion to the usb mass storage driver, and add a new try_disconnect
> callback for usb drivers. I'm not saying this is going to be completely
> straight forward, but it ain't rocket science either. And it so very
> obviously is the right thing to do, that I'm getting very tired of
> the do it in userspace song I keep hearing.
Doing a try_disconnect() would also solve the dual camera issue.
But it doesn't really interfere with the user space vs. kernel space
issue. You simply have to expand the ioctl interface to have
an ioctl that triggers this API call in the kernel.
A V4L2 device would return an error if its device node is opened,
otherwise disconnect.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists