From: Pekka Enberg <[EMAIL PROTECTED]>

This documents revoke file operation in Documentation/filesystems/vfs.txt.

Signed-off-by: Pekka Enberg <[EMAIL PROTECTED]>
---

 Documentation/filesystems/vfs.txt |    5 +++++
 1 file changed, 5 insertions(+)

Index: 2.6/Documentation/filesystems/vfs.txt
===================================================================
--- 2.6.orig/Documentation/filesystems/vfs.txt  2007-05-21 15:37:59.000000000 
+0300
+++ 2.6/Documentation/filesystems/vfs.txt       2007-07-11 11:48:46.000000000 
+0300
@@ -732,6 +732,7 @@ struct file_operations {
 int);
        ssize_t (*splice_read)(struct file *, struct pipe_inode_info *, size_t, 
unsigned  
 int);
+       int (*revoke)(struct file *);
 };
 
 Again, all methods are called without any locks being held, unless
@@ -805,6 +806,10 @@ otherwise noted.
   splice_read: called by the VFS to splice data from file to a pipe. This
               method is used by the splice(2) system call
 
+  revoke: called by revokeat(2) and frevoke(2) system calls to revoke access
+         to an open file. This method must ensure that all currently blocked
+         writes are flushed and reads will fail.
+
 Note that the file operations are implemented by the specific
 filesystem in which the inode resides. When opening a device node
 (character or block special) most filesystems will call special
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to