From 78c2cc25d5537063ae3a6f94578e1db2bb9ba0b6 Mon Sep 17 00:00:00 2001 From: Miklos Szeredi Date: Fri, 20 Jul 2012 09:45:09 +0200 Subject: Remove compatibility path handling This means that now NULL is a valid path for operations that take a file descriptor if the file was unlinked and hard_remove option is specified. --- include/fuse.h | 21 ++++----------------- 1 file changed, 4 insertions(+), 17 deletions(-) (limited to 'include/fuse.h') diff --git a/include/fuse.h b/include/fuse.h index 7522cb6..a23dadb 100644 --- a/include/fuse.h +++ b/include/fuse.h @@ -446,18 +446,6 @@ struct fuse_operations { */ int (*bmap) (const char *, size_t blocksize, uint64_t *idx); - /** - * Flag indicating that the filesystem can accept a NULL path - * as the first argument for the following operations: - * - * read, write, flush, release, fsync, readdir, releasedir, - * fsyncdir, ftruncate, fgetattr, lock, ioctl and poll - * - * If this flag is set these operations continue to work on - * unlinked files even if "-ohard_remove" option was specified. - */ - unsigned int flag_nullpath_ok:1; - /** * Flag indicating that the path need not be calculated for * the following operations: @@ -465,10 +453,9 @@ struct fuse_operations { * read, write, flush, release, fsync, readdir, releasedir, * fsyncdir, ftruncate, fgetattr, lock, ioctl and poll * - * Closely related to flag_nullpath_ok, but if this flag is - * set then the path will not be calculaged even if the file - * wasn't unlinked. However the path can still be non-NULL if - * it needs to be calculated for some other reason. + * If this flag is set then the path will not be calculaged even if the + * file wasn't unlinked. However the path can still be non-NULL if it + * needs to be calculated for some other reason. */ unsigned int flag_nopath:1; @@ -481,7 +468,7 @@ struct fuse_operations { /** * Reserved flags, don't set */ - unsigned int flag_reserved:29; + unsigned int flag_reserved:30; /** * Ioctl -- cgit v1.2.3