[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220616040411.5vsnxz5fc4yq4zri@riteshh-domain>
Date: Thu, 16 Jun 2022 09:34:11 +0530
From: Ritesh Harjani <ritesh.list@...il.com>
To: Baokun Li <libaokun1@...wei.com>
Cc: linux-ext4@...r.kernel.org, tytso@....edu,
adilger.kernel@...ger.ca, jack@...e.cz, lczerner@...hat.com,
enwlinux@...il.com, linux-kernel@...r.kernel.org,
yi.zhang@...wei.com, yebin10@...wei.com, yukuai3@...wei.com
Subject: Re: [PATCH v3 3/4] ext4: correct max_inline_xattr_value_size
computing
On 22/06/16 10:13AM, Baokun Li wrote:
> If the ext4 inode does not have xattr space, 0 is returned in the
> get_max_inline_xattr_value_size function. Otherwise, the function returns
> a negative value when the inode does not contain EXT4_STATE_XATTR.
Yes, this looks good to me.
Feel free to add -
Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@...il.com>
>
> Signed-off-by: Baokun Li <libaokun1@...wei.com>
> ---
> fs/ext4/inline.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/ext4/inline.c b/fs/ext4/inline.c
> index cff52ff6549d..da5de43623dd 100644
> --- a/fs/ext4/inline.c
> +++ b/fs/ext4/inline.c
> @@ -35,6 +35,9 @@ static int get_max_inline_xattr_value_size(struct inode *inode,
> struct ext4_inode *raw_inode;
> int free, min_offs;
>
> + if (!EXT4_INODE_HAS_XATTR_SPACE(inode))
> + return 0;
> +
> min_offs = EXT4_SB(inode->i_sb)->s_inode_size -
> EXT4_GOOD_OLD_INODE_SIZE -
> EXT4_I(inode)->i_extra_isize -
> --
> 2.31.1
>
Powered by blists - more mailing lists