[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0703091015460.32320@sbz-30.cs.Helsinki.FI>
Date: Fri, 9 Mar 2007 10:16:09 +0200 (EET)
From: Pekka J Enberg <penberg@...helsinki.fi>
To: akpm@...ux-foundation.org
cc: linux-kernel@...r.kernel.org, hch@...radead.org,
alan@...rguk.ukuu.org.uk, serue@...ibm.com
Subject: [PATCH 5/7] revoke: add documentation
From: Pekka Enberg <penberg@...helsinki.fi>
This documents revoke file operation in Documentation/filesystems/vfs.txt.
Signed-off-by: Pekka Enberg <penberg@...helsinki.fi>
---
Documentation/filesystems/vfs.txt | 5 +++++
1 file changed, 5 insertions(+)
Index: uml-2.6/Documentation/filesystems/vfs.txt
===================================================================
--- uml-2.6.orig/Documentation/filesystems/vfs.txt 2007-03-08 10:24:23.000000000 +0200
+++ uml-2.6/Documentation/filesystems/vfs.txt 2007-03-08 10:24:33.000000000 +0200
@@ -732,6 +732,7 @@
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 @@
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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists