[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac3eb2510905221124y412dc3bdp65ad1b74373175a9@mail.gmail.com>
Date: Fri, 22 May 2009 20:24:15 +0200
From: Kay Sievers <kay.sievers@...y.org>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>,
Kyle Moffett <kyle@...fetthome.net>,
Pantelis Koukousoulas <pktoss@...il.com>,
Al Viro <viro@...iv.linux.org.uk>,
Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: How to tell whether a struct file is held by a process?
On Fri, May 22, 2009 at 17:54, Alan Stern <stern@...land.harvard.edu> wrote:
>> Would releasing the "lock" trigger a kernel-driver-binding call?
>
> No. If the lock owner wants to bind kernel drivers, it can use the
> existing API in libusb after releasing the lock. This might cause
> problems if the owning process terminates abnormally, but I think we
> can live with that.
>
>> The lock will always lock all devices of a specific hub?
>
> The idea is that there will be one lock file per port. So for example,
> a hub device with four ports might contain inside its sysfs device
> directory: ports/1, ..., ports/4.
Sounds both good to me.
Kay
--
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