summaryrefslogtreecommitdiffstats
path: root/fs/ext4/file.c
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2019-06-09 22:04:33 -0400
committerTheodore Ts'o <tytso@mit.edu>2019-06-09 22:04:33 -0400
commit02b016ca7f99229ae6227e7b2fc950c4e140d74a (patch)
treeb372e85bc1d9c11dca0d949f713723d4b6a648da /fs/ext4/file.c
parent2e53840362771c73eb0a5ff71611507e64e8eecd (diff)
ext4: enforce the immutable flag on open files
According to the chattr man page, "a file with the 'i' attribute cannot be modified..." Historically, this was only enforced when the file was opened, per the rest of the description, "... and the file can not be opened in write mode". There is general agreement that we should standardize all file systems to prevent modifications even for files that were opened at the time the immutable flag is set. Eventually, a change to enforce this at the VFS layer should be landing in mainline. Until then, enforce this at the ext4 level to prevent xfstests generic/553 from failing. Signed-off-by: Theodore Ts'o <tytso@mit.edu> Cc: "Darrick J. Wong" <darrick.wong@oracle.com> Cc: stable@kernel.org
Diffstat (limited to 'fs/ext4/file.c')
-rw-r--r--fs/ext4/file.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/fs/ext4/file.c b/fs/ext4/file.c
index 2c5baa5e8291..f4a24a46245e 100644
--- a/fs/ext4/file.c
+++ b/fs/ext4/file.c
@@ -165,6 +165,10 @@ static ssize_t ext4_write_checks(struct kiocb *iocb, struct iov_iter *from)
165 ret = generic_write_checks(iocb, from); 165 ret = generic_write_checks(iocb, from);
166 if (ret <= 0) 166 if (ret <= 0)
167 return ret; 167 return ret;
168
169 if (unlikely(IS_IMMUTABLE(inode)))
170 return -EPERM;
171
168 /* 172 /*
169 * If we have encountered a bitmap-format file, the size limit 173 * If we have encountered a bitmap-format file, the size limit
170 * is smaller than s_maxbytes, which is for extent-mapped files. 174 * is smaller than s_maxbytes, which is for extent-mapped files.