From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
Add the ->revoke() file operation to VFS documentation.
Cc: Alan Cox <alan@xxxxxxxxxx>
Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Signed-off-by: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
---
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-11-23 09:58:11.000000000 +0200
+++ 2.6/Documentation/filesystems/vfs.txt 2007-12-14 16:41:05.000000000 +0200
@@ -780,6 +780,7 @@ struct file_operations {
int (*flock) (struct file *, int, struct file_lock *);
ssize_t (*splice_write)(struct pipe_inode_info *, struct file *, size_t, unsigned 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
@@ -853,6 +854,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) system call to revoke access to an open file.
+ This method must ensure that all currently blocked writes are flushed
+ and that all pending 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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
