diff options
| author | Mark Fasheh <[email protected]> | 2018-09-10 16:21:18 -0700 |
|---|---|---|
| committer | Al Viro <[email protected]> | 2018-10-17 21:15:39 -0400 |
| commit | 85c95f208f481ab3c34c4622f508272cd4803afd (patch) | |
| tree | 8d1fdc72d85e38d2eaa245de006ac3e4cb8adde6 | |
| parent | 5de4480ae7f8f1969065aa88be98111e36075bb0 (diff) | |
vfs: dedupe should return EPERM if permission is not granted
Right now we return EINVAL if a process does not have permission to dedupe a
file. This was an oversight on my part. EPERM gives a true description of
the nature of our error, and EINVAL is already used for the case that the
filesystem does not support dedupe.
Signed-off-by: Mark Fasheh <[email protected]>
Reviewed-by: Darrick J. Wong <[email protected]>
Acked-by: David Sterba <[email protected]>
Signed-off-by: Al Viro <[email protected]>
| -rw-r--r-- | fs/read_write.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/read_write.c b/fs/read_write.c index be0e8723a049..c734bc2880a5 100644 --- a/fs/read_write.c +++ b/fs/read_write.c @@ -1991,7 +1991,7 @@ int vfs_dedupe_file_range_one(struct file *src_file, loff_t src_pos, if (ret < 0) goto out_drop_write; - ret = -EINVAL; + ret = -EPERM; if (!allow_file_dedupe(dst_file)) goto out_drop_write; |