Skip to contentSkip to conversation

revoke/frevoke system calls

RFC/PATCH Bodo Eggert 2 participants 2 messages Jul 20, 2006 1 message not in the archive VFS

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 8 lines · Pekka J Enberg

From: Pekka Enberg <[email protected]>

This patch implements the revoke(2) and frevoke(2) system calls for all types of files. We revoke files in two passes: first we scan all open files that refer to the inode and substitute the struct file pointer in fd table with NULL causing all subsequent operations on that fd to fail. After we have done that to all file descriptors, we close the files and take down mmaps.

RFC2: Make umount -f work on local fs using this feature.

Signature · 8 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.

http://david.woodhou.se/why-not-spf.html
-
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
#2 lore raw
Quoted 11 lines · Bodo Eggert
Quoted 8 lines · Pekka J Enberg

From: Pekka Enberg <[email protected]>

This patch implements the revoke(2) and frevoke(2) system calls for all types of files. We revoke files in two passes: first we scan all open files that refer to the inode and substitute the struct file pointer in fd table with NULL causing all subsequent operations on that fd to fail. After we have done that to all file descriptors, we close the files and take down mmaps.

RFC2: Make umount -f work on local fs using this feature.

RFC3: use preliminary work about umount -f in order to get revoke for free. See for instance
http://developer.osdl.org/dev/fumount/kernel2/patches/2.6.12/1/forced-unmount-2.6.12-1.patch