From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Utkal Singh <singhutkal015@gmail.com>, linux-erofs@lists.ozlabs.org
Cc: xiang@kernel.org
Subject: Re: [PATCH v2] erofs-utils: lib: harden h_shared_count in erofs_init_inode_xattrs()
Date: Tue, 17 Mar 2026 23:25:33 +0800 [thread overview]
Message-ID: <e7285eaa-281e-4a5e-adc6-8af88b166b43@linux.alibaba.com> (raw)
In-Reply-To: <20260317151514.3529-1-singhutkal015@gmail.com>
On 2026/3/17 23:15, Utkal Singh wrote:
> `u8 h_shared_count` indicates the shared xattr count of an inode. It is
> read from the on-disk xattr ibody header, which should be corrupted if
> the size of the shared xattr array exceeds the space available in
> `xattr_isize`.
>
> It does not cause harmful consequence (e.g. crashes), since the image is
> already considered corrupted, it indeed results in the silent processing
> of garbage metadata.
>
> Let's harden it to report -EFSCORRUPTED earlier.
>
> Reproducer:
> mkdir testdir && echo hello > testdir/a.txt
> setfattr -n user.test -v val testdir/a.txt
> mkfs.erofs test.img testdir
> # corrupt h_shared_count (offset = nid*32 + inode_size + 4) to 0xFF
> # then: fsck.erofs --extract=/tmp/out --xattrs test_corrupted.img
> # Without patch: silently processes invalid shared xattr IDs
> # With patch: returns -EFSCORRUPTED
>
> Signed-off-by: Utkal Singh <singhutkal015@gmail.com>
> ---
> lib/xattr.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/lib/xattr.c b/lib/xattr.c
> index 565070a..9d52a18 100644
> --- a/lib/xattr.c
> +++ b/lib/xattr.c
> @@ -1182,6 +1182,13 @@ static int erofs_init_inode_xattrs(struct erofs_inode *vi)
>
> ih = it.kaddr;
> vi->xattr_shared_count = ih->h_shared_count;
> + if (vi->xattr_shared_count * sizeof(__le32) >
> + vi->xattr_isize - sizeof(struct erofs_xattr_ibody_header)) {
> + erofs_err("invalid h_shared_count %u in nid %llu",
I think this line is incorrect (did you compile at least?), also
you need to Cc LKML <linux-kernel@vger.kernel.org> for all
kernel patches.
Thanks,
Gao Xiang
next prev parent reply other threads:[~2026-03-17 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 15:15 [PATCH v2] erofs-utils: lib: harden h_shared_count in erofs_init_inode_xattrs() Utkal Singh
2026-03-17 15:25 ` Gao Xiang [this message]
2026-03-17 15:27 ` 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=e7285eaa-281e-4a5e-adc6-8af88b166b43@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=singhutkal015@gmail.com \
--cc=xiang@kernel.org \
/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