lkml.org 
[lkml]   [2009]   [May]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: How to tell whether a struct file is held by a process?
On Fri, 22 May 2009, Kay Sievers wrote:

> On Fri, May 22, 2009 at 17:54, Alan Stern <stern@rowland.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.

Come to think of it, putting the lock files in sysfs isn't such a good
idea. The core will need to know whether the files are open, so we'll
have to have our own file_operations structure for them.

Which means the best place to put the lock files is probably somewhere
in /dev. Can this be made to work by generating appropriate uevents,
with the default udev rules?

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2009-05-22 21:33    [W:0.147 / U:0.400 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site