On Thu, 17 Jun 1999 10:58:02 -0700, Bob Miller <kbob@jogger-egg.engr.sgi.com> said:
> 1. Define a new flag in struct file. Call it F_NOKLOCK.
> (This flag should not be user-visible, so I don't think it
> can go in f_flags. But somewhere in struct file, because
> that's the toplevel data structure, and the toplevel
> routines grab the lock.)
This can be done inside the driver's own strategy routine if it is safe
to do so for that driver: no VFS changes are needed. The upper VFS
layers are already safe in this respect, because they need to be
prepared for an implicit drop of the lock if we take a page fault while
doing the user-space copy.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/