From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Jia Zhu <zhujia.zj@bytedance.com>, Gao Xiang <xiang@kernel.org>,
Chao Yu <chao@kernel.org>
Cc: linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Yue Hu <zbestahu@gmail.com>,
Jeffle Xu <jefflexu@linux.alibaba.com>,
Sandeep Dhavale <dhavale@google.com>,
Hongbo Li <lihongbo22@huawei.com>,
Chunhai Guo <guochunhai@vivo.com>,
Amir Goldstein <amir73il@gmail.com>
Subject: Re: [PATCH] erofs: fix metabuf leak in shared xattr initialization
Date: Wed, 20 May 2026 12:41:49 +0800 [thread overview]
Message-ID: <cc1beea0-6a1d-456c-9dda-8b2ac6e5848c@linux.alibaba.com> (raw)
In-Reply-To: <d6707821-fe25-4331-94bf-c0c3936c8d1f@linux.alibaba.com>
On 2026/5/20 12:25, Gao Xiang wrote:
> Hi Jia,
>
> On 2026/5/20 11:42, Jia Zhu wrote:
>> erofs_init_inode_xattrs() uses a local metabuf while reading the inline
>> xattr header and the shared xattr id array.
>>
>> It currently drops that metabuf from some error paths and from the success
>> path, but the erofs_bread() failure while reading the shared xattr id array
>> goes straight to out_unlock.
>>
>> This became observable when file-backed metadata reads started calling
>> rw_verify_area() before reusing or dropping the current metabuf. Before
>> that, the read_mapping_folio() failure path already dropped the old metabuf
>> before returning an error.
even it's exposable directly due to commit 307210c262a2
"erofs: verify metadata accesses for file-backed mounts")
I still hope we could mark it as an xattr implementaion
issue instead of a random consequence, we should
erofs_put_metabuf() as long as `erofs_buf` was
successfully used once.
>>
>> Consolidate the local metabuf cleanup at out_unlock. erofs_put_metabuf()
>> is a no-op if no page has been acquired, and this keeps all paths after
>> taking EROFS_I_BL_XATTR_BIT covered by one cleanup site.
>>
>> Fixes: 307210c262a2 ("erofs: verify metadata accesses for file-backed mounts")
>
>
> Hmm, I don't think it's a correct "Fixes:", and
> the commit message should be fixed too.
>
> I think it's an issue due to missing erofs_put_metabuf()
> in the erofs_init_inode_xattrs() error path instead.
>
> I think
> Fixes: bb88e8da0025 ("erofs: use meta buffers for xattr operations")
>
> is a more proper "Fixes:".
>
> Thanks,
> Gao Xiang
>
>> Signed-off-by: Jia Zhu <zhujia.zj@bytedance.com>
>> ---
>> fs/erofs/xattr.c | 4 +---
>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/fs/erofs/xattr.c b/fs/erofs/xattr.c
>> index 41e311019a251..df7ea019526d7 100644
>> --- a/fs/erofs/xattr.c
>> +++ b/fs/erofs/xattr.c
>> @@ -89,13 +89,11 @@ static int erofs_init_inode_xattrs(struct inode *inode)
>> vi->xattr_isize - sizeof(struct erofs_xattr_ibody_header)) {
>> erofs_err(sb, "invalid h_shared_count %u @ nid %llu",
>> vi->xattr_shared_count, vi->nid);
>> - erofs_put_metabuf(&buf);
>> ret = -EFSCORRUPTED;
>> goto out_unlock;
>> }
>> vi->xattr_shared_xattrs = kmalloc_objs(uint, vi->xattr_shared_count);
>> if (!vi->xattr_shared_xattrs) {
>> - erofs_put_metabuf(&buf);
>> ret = -ENOMEM;
>> goto out_unlock;
>> }
>> @@ -112,12 +110,12 @@ static int erofs_init_inode_xattrs(struct inode *inode)
>> }
>> vi->xattr_shared_xattrs[i] = le32_to_cpu(*xattr_id);
>> }
>> - erofs_put_metabuf(&buf);
>> /* paired with smp_mb() at the beginning of the function. */
>> smp_mb();
>> set_bit(EROFS_I_EA_INITED_BIT, &vi->flags);
>> out_unlock:
>> + erofs_put_metabuf(&buf);
>> clear_and_wake_up_bit(EROFS_I_BL_XATTR_BIT, &vi->flags);
>> return ret;
>> }
>
next prev parent reply other threads:[~2026-05-20 4:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 3:42 Jia Zhu
2026-05-20 4:25 ` Gao Xiang
2026-05-20 4:41 ` Gao Xiang [this message]
2026-05-20 4:46 ` [PATCH v2] erofs: fix metabuf leak in inode " Jia Zhu
2026-05-20 6:36 ` Gao Xiang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cc1beea0-6a1d-456c-9dda-8b2ac6e5848c@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=amir73il@gmail.com \
--cc=chao@kernel.org \
--cc=dhavale@google.com \
--cc=guochunhai@vivo.com \
--cc=jefflexu@linux.alibaba.com \
--cc=lihongbo22@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@kernel.org \
--cc=zbestahu@gmail.com \
--cc=zhujia.zj@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome