On Thu, Jul 19, 2007 at 01:41:03PM +0200, Jan Engelhardt wrote:
>
> On Jul 19 2007 02:01, Jacob A wrote:
> >
> > How can a device driver go over the list of all the files that are open on a
> > specific inode instance?
>
> pseudo-code:
>
> task_list_lock;
> for each process; do
> lock_fdtable;
> for each filedescriptor; do
> do_something(fd->file_ptr);
> unlock_fdtable;
> task_list_unlock;
Not again...
There are other things that can keep file open. SCM_RIGHTS, references
held by syscall in progress, etc., etc.
The real question is why does driver want to do that? Details, please...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
