diff options
| author | Chao Yu <chao@kernel.org> | 2022-05-17 11:37:23 +0800 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2022-05-18 15:36:09 -0700 |
| commit | 958ed92922028ec67f504dcdc72bfdfd0f43936a (patch) | |
| tree | 9b0650adf8db05cdaac745fd94afaa85843c91d2 /fs/f2fs | |
| parent | b5639bb4313b9d455fc9fc4768d23a5e4ca8cb9d (diff) | |
| download | linux-958ed92922028ec67f504dcdc72bfdfd0f43936a.tar.gz linux-958ed92922028ec67f504dcdc72bfdfd0f43936a.tar.bz2 linux-958ed92922028ec67f504dcdc72bfdfd0f43936a.zip | |
f2fs: fix fallocate to use file_modified to update permissions consistently
This patch tries to fix permission consistency issue as all other
mainline filesystems.
Since the initial introduction of (posix) fallocate back at the turn of
the century, it has been possible to use this syscall to change the
user-visible contents of files. This can happen by extending the file
size during a preallocation, or through any of the newer modes (punch,
zero, collapse, insert range). Because the call can be used to change
file contents, we should treat it like we do any other modification to a
file -- update the mtime, and drop set[ug]id privileges/capabilities.
The VFS function file_modified() does all this for us if pass it a
locked inode, so let's make fallocate drop permissions correctly.
Cc: stable@kernel.org
Signed-off-by: Chao Yu <chao.yu@oppo.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs')
| -rw-r--r-- | fs/f2fs/file.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index 216081ea8c81..7aac53ac5acf 100644 --- a/fs/f2fs/file.c +++ b/fs/f2fs/file.c @@ -1780,6 +1780,10 @@ static long f2fs_fallocate(struct file *file, int mode, inode_lock(inode); + ret = file_modified(file); + if (ret) + goto out; + if (mode & FALLOC_FL_PUNCH_HOLE) { if (offset >= inode->i_size) goto out; |