[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47a91a45-7e36-45e0-891f-475adca77f59@linux.alibaba.com>
Date: Fri, 28 Jun 2024 15:30:35 +0800
From: Gao Xiang <hsiangkao@...ux.alibaba.com>
To: libaokun@...weicloud.com, netfs@...ts.linux.dev, dhowells@...hat.com,
jlayton@...nel.org
Cc: jefflexu@...ux.alibaba.com, zhujia.zj@...edance.com,
linux-erofs@...ts.ozlabs.org, brauner@...nel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
yangerkun@...wei.com, houtao1@...wei.com, yukuai3@...wei.com,
wozizhi@...wei.com, Baokun Li <libaokun1@...wei.com>
Subject: Re: [PATCH v3 4/9] cachefiles: propagate errors from vfs_getxattr()
to avoid infinite loop
On 2024/6/28 14:29, libaokun@...weicloud.com wrote:
> From: Baokun Li <libaokun1@...wei.com>
>
> In cachefiles_check_volume_xattr(), the error returned by vfs_getxattr()
> is not passed to ret, so it ends up returning -ESTALE, which leads to an
> endless loop as follows:
>
> cachefiles_acquire_volume
> retry:
> ret = cachefiles_check_volume_xattr
> ret = -ESTALE
> xlen = vfs_getxattr // return -EIO
> // The ret is not updated when xlen < 0, so -ESTALE is returned.
> return ret
> // Supposed to jump out of the loop at this judgement.
> if (ret != -ESTALE)
> goto error_dir;
> cachefiles_bury_object
> // EIO causes rename failure
> goto retry;
>
> Hence propagate the error returned by vfs_getxattr() to avoid the above
> issue. Do the same in cachefiles_check_auxdata().
>
> Fixes: 32e150037dce ("fscache, cachefiles: Store the volume coherency data")
> Fixes: 72b957856b0c ("cachefiles: Implement metadata/coherency data storage in xattrs")
> Signed-off-by: Baokun Li <libaokun1@...wei.com>
It looks good to me,
Reviewed-by: Gao Xiang <hsiangkao@...ux.alibaba.com>
Thanks,
Gao Xiang
Powered by blists - more mailing lists