fs,fsverity: remove check for fsverity being enabled in setattr_prepare()

The check that fs-verity is available in the kernel is not necessary
here. Filesystems could have fsverity files even without fs-verity
enabled. In that case, truncate on fsverity file will succeed, what this
check is trying to prevent.

Fixes: e9734653c523 ("fs,fsverity: reject size changes on fsverity files in setattr_prepare")
Cc: stable@vger.kernel.org
Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Link: https://patch.msgid.link/20260727094352.1734826-1-aalbersh@kernel.org
Signed-off-by: Eric Biggers <ebiggers@kernel.org>

diff --git a/fs/attr.c b/fs/attr.c
index 4f437fabb7f0f59682895d64dc8301b9927ce39d..71888ac903c27ddacc51dfd64e3be58f868d7e20 100644 (file)
--- a/fs/attr.c
+++ b/fs/attr.c
@@ -176,7 +176,7 @@ int setattr_prepare(struct mnt_idmap *idmap, struct dentry *dentry,
                 * covered by the open-time check because sys_truncate() takes a
                 * path, not an open file.
                 */
-               if (IS_ENABLED(CONFIG_FS_VERITY) && IS_VERITY(inode))
+               if (IS_VERITY(inode))
                        return -EPERM;
 
                error = inode_newsize_ok(inode, attr->ia_size);