diff options
| author | Niels de Vos <ndevos@redhat.com> | 2018-08-21 15:36:31 +0300 |
|---|---|---|
| committer | Miklos Szeredi <mszeredi@redhat.com> | 2018-09-28 17:43:22 +0300 |
| commit | 88bc7d5097a11d9bdcf08ecf85c81ba998353437 (patch) | |
| tree | 40bceda7dc1db073a51d8ed34675073fbf70dfd0 /fs/fuse/fuse_i.h | |
| parent | 908a572b80f6e9577b45e81b3dfe2e22111286b8 (diff) | |
| download | linux-88bc7d5097a11d9bdcf08ecf85c81ba998353437.tar.xz | |
fuse: add support for copy_file_range()
There are several FUSE filesystems that can implement server-side copy
or other efficient copy/duplication/clone methods. The copy_file_range()
syscall is the standard interface that users have access to while not
depending on external libraries that bypass FUSE.
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'fs/fuse/fuse_i.h')
| -rw-r--r-- | fs/fuse/fuse_i.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/fs/fuse/fuse_i.h b/fs/fuse/fuse_i.h index f78e9614bb5f..3e45d408a644 100644 --- a/fs/fuse/fuse_i.h +++ b/fs/fuse/fuse_i.h @@ -637,6 +637,9 @@ struct fuse_conn { /** Allow other than the mounter user to access the filesystem ? */ unsigned allow_other:1; + /** Does the filesystem support copy_file_range? */ + unsigned no_copy_file_range:1; + /** The number of requests waiting for completion */ atomic_t num_waiting; |