[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181127002915.GC11663@gmail.com>
Date: Mon, 26 Nov 2018 16:29:16 -0800
From: Eric Biggers <ebiggers@...nel.org>
To: "Theodore Y. Ts'o" <tytso@....edu>
Cc: Chandan Rajendra <chandan@...ux.vnet.ibm.com>,
linux-fscrypt@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: [PATCH 5/7] ext4: use IS_VERITY() to check inode's fsverity
status
On Mon, Nov 26, 2018 at 12:36:15PM -0500, Theodore Y. Ts'o wrote:
> On Mon, Nov 19, 2018 at 10:53:22AM +0530, Chandan Rajendra wrote:
> > This commit now uses IS_VERITY() macro to check if fsverity is
> > enabled on an inode.
> >
> > Signed-off-by: Chandan Rajendra <chandan@...ux.vnet.ibm.com>
>
> This patch causes a massive number of fsverity tests. I suspect it's
> due to a mismatch between the ext4's inode flags as opposed to the VFS
> inode's flags. I'll take a closer look in the next day or two.
>
> Cheers,
>
> - Ted
It's missing the following to set S_VERITY during the
FS_IOC_ENABLE_VERITY ioctl:
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index ed933e64e95f..82b45cceb39b 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -1344,6 +1344,11 @@ static int ext4_set_verity(struct inode *inode, loff_t data_i_size)
err = ext4_reserve_inode_write(handle, inode, &iloc);
if (err == 0) {
ext4_set_inode_flag(inode, EXT4_INODE_VERITY);
+ /*
+ * Update inode->i_flags - S_VERITY will be enabled,
+ * S_DAX may be disabled
+ */
+ ext4_set_inode_flags(inode);
EXT4_I(inode)->i_disksize = data_i_size;
err = ext4_mark_iloc_dirty(handle, inode, &iloc);
}
Powered by blists - more mailing lists