diff options
| author | Miklos Szeredi <mszeredi@suse.cz> | 2008-05-12 14:02:32 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2008-05-13 08:02:26 -0700 |
| commit | 78bb6cb9a890d3d50ca3b02fce9223d3e734ab9b (patch) | |
| tree | 330cc4fd17af9176ae9e2ee833e1097638fd1b30 /include/linux/fuse.h | |
| parent | 0f146a764ff08c4c210c04239c5e6784b4b77485 (diff) | |
| download | linux-3.10-78bb6cb9a890d3d50ca3b02fce9223d3e734ab9b.tar.gz linux-3.10-78bb6cb9a890d3d50ca3b02fce9223d3e734ab9b.tar.bz2 linux-3.10-78bb6cb9a890d3d50ca3b02fce9223d3e734ab9b.zip | |
fuse: add flag to turn on big writes
Prior to 2.6.26 fuse only supported single page write requests. In theory all
fuse filesystem should be able support bigger than 4k writes, as there's
nothing in the API to prevent it. Unfortunately there's a known case in
NTFS-3G where big writes cause filesystem corruption. There could also be
other filesystems, where the lack of testing with big write requests would
result in bugs.
To prevent such problems on a kernel upgrade, disable big writes by default,
but let filesystems set a flag to turn it on.
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
Cc: Szabolcs Szakacsits <szaka@ntfs-3g.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/fuse.h')
| -rw-r--r-- | include/linux/fuse.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/fuse.h b/include/linux/fuse.h index 5c86f1196c3..d4828219769 100644 --- a/include/linux/fuse.h +++ b/include/linux/fuse.h @@ -109,6 +109,7 @@ struct fuse_file_lock { #define FUSE_POSIX_LOCKS (1 << 1) #define FUSE_FILE_OPS (1 << 2) #define FUSE_ATOMIC_O_TRUNC (1 << 3) +#define FUSE_BIG_WRITES (1 << 5) /** * Release flags |