summaryrefslogtreecommitdiff
path: root/Kbuild
diff options
context:
space:
mode:
authorAdam Borowski <kilobyte@angband.pl>2018-07-18 00:08:59 +0200
committerDavid Sterba <dsterba@suse.com>2018-08-06 13:12:58 +0200
commit616d374efa23cb699074ea02b301254ad64d224a (patch)
treedb5a02bf91b2df5f0d38140a648093783b75cdf0 /Kbuild
parent3c4276936f6fbe52884b4ea4e6cc120b890a0f9f (diff)
downloadlinux-616d374efa23cb699074ea02b301254ad64d224a.tar.gz
linux-616d374efa23cb699074ea02b301254ad64d224a.tar.bz2
linux-616d374efa23cb699074ea02b301254ad64d224a.zip
btrfs: allow defrag on a file opened read-only that has rw permissions
Requiring a read-write descriptor conflicts both ways with exec, returning ETXTBSY whenever you try to defrag a program that's currently being run, or causing intermittent exec failures on a live system being defragged. As defrag doesn't change the file's contents in any way, there's no reason to consider it a rw operation. Thus, let's check only whether the file could have been opened rw. Such access control is still needed as currently defrag can use extra disk space, and might trigger bugs. We return EINVAL when the request is invalid; here it's ok but merely the user has insufficient privileges. Thus, the EPERM return value reflects the error better -- as discussed in the identical case for dedupe. According to codesearch.debian.net, no userspace program distinguishes these values beyond strerror(). Signed-off-by: Adam Borowski <kilobyte@angband.pl> Reviewed-by: David Sterba <dsterba@suse.com> [ fold the EPERM patch from Adam ] Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions