From: Kay Sievers <kay.sievers@vrfy.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Kyle Moffett <kyle@moffetthome.net>,
Pantelis Koukousoulas <pktoss@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: How to tell whether a struct file is held by a process?
Date: Sun, 24 May 2009 00:47:51 +0200 [thread overview]
Message-ID: <ac3eb2510905231547y6da1b3a6m6ef8921c8f56dc00@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0905221801470.22960-100000@iolanthe.rowland.org>
On Sat, May 23, 2009 at 00:07, Alan Stern <stern@rowland.harvard.edu> wrote:
>> Can't we just add ioctls to the hub device
>> nodes to implement the locking?
>
> Yes, that would work. Closing the hub device file would release all
> the locked ports.
>
> It wouldn't leave any lock files for user programs. They would have to
> arrange the locking among themselves somehow. Would that be okay?
I would expect that userspace drivers competing about raw USB devices
wouldn't be that common. And I guess, most of these problems can
probably be solved by simple file permissions/ACLs applied to the USB
device nodes, in the same way the access to the hub device node would
be granted to lock-out the kernel drivers.
Kay
next prev parent reply other threads:[~2009-05-23 22:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 16:57 Alan Stern
2009-05-21 9:52 ` Al Viro
2009-05-21 14:06 ` Alan Stern
2009-05-21 21:07 ` Kay Sievers
2009-05-21 21:27 ` Alan Stern
2009-05-22 13:30 ` Pantelis Koukousoulas
2009-05-22 13:38 ` Oliver Neukum
2009-05-22 13:43 ` Alan Cox
2009-05-22 13:52 ` Pantelis Koukousoulas
2009-05-22 14:12 ` Alan Cox
2009-05-22 14:29 ` Pantelis Koukousoulas
2009-05-21 22:14 ` Alan Cox
2009-05-22 1:28 ` Kyle Moffett
2009-05-22 9:53 ` Alan Cox
2009-05-22 15:12 ` Alan Stern
2009-05-22 15:20 ` Alan Cox
2009-05-22 16:04 ` Alan Stern
2009-05-22 16:23 ` Pantelis Koukousoulas
2009-05-22 18:19 ` Alan Stern
2009-05-22 15:21 ` Kay Sievers
2009-05-22 15:54 ` Alan Stern
2009-05-22 18:24 ` Kay Sievers
2009-05-22 18:48 ` Pantelis Koukousoulas
2009-05-22 19:31 ` Alan Stern
2009-05-22 21:54 ` Kay Sievers
2009-05-22 22:07 ` Alan Stern
2009-05-23 22:47 ` Kay Sievers [this message]
2009-05-22 8:36 ` Oliver Neukum
2009-05-21 22:22 ` Alan Cox
2009-05-22 12:26 ` Oliver Neukum
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=ac3eb2510905231547y6da1b3a6m6ef8921c8f56dc00@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kyle@moffetthome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pktoss@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=viro@zeniv.linux.org.uk \
/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®