Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: Wenyuan Xu <sereno.xu@deepseek.com>
Cc: xiang@kernel.org, linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH] erofs-utils: fsck: extract zero-length xattr values
Date: Wed, 4 Nov 2026 09:36:47 +0100	[thread overview]
Message-ID: <aurunz5-1b4visC4@XiangdeMacBook-Pro.local> (raw)
In-Reply-To: <20261104035208.2471090-1-sereno.xu@deepseek.com>

Hi Wenyuan,

On Wed, Nov 04, 2026 at 03:52:08AM +0000, Wenyuan Xu wrote:
> A zero return value from erofs_getxattr() denotes an empty attribute,
> but the extraction path treats it as an error.
> 
> Accept zero-length values and allocate at least one byte for the value
> buffer, avoiding dependence on malloc(0) behavior.
> 
> Signed-off-by: Wenyuan Xu <sereno.xu@deepseek.com>

According to
https://linux.die.net/man/2/getxattr

Return Value
On success, a positive number is returned indicating the
size of the extended attribute value.

So 0-sized xattrs are not a valid number or here is a mistake.

In principle, filesystems accept 0-size xattrs, and
overlayfs uses it (see ovl_path_check_origin_xattr()).

I think EROFS should support 0-size xattrs, but here
we shouldn't expand to 1.

I applied the following diff (please find if it works or not):

diff --git a/fsck/main.c b/fsck/main.c
index 8e3ae52..1a36ef8 100644
--- a/fsck/main.c
+++ b/fsck/main.c
@@ -458,25 +458,33 @@ static int erofsfsck_dump_xattrs(struct erofs_inode *inode)
 		size_t size = 0;
 
 		ret = erofs_getxattr(inode, key, NULL, 0);
-		if (ret <= 0) {
+		if (ret < 0) {
 			DBG_BUGON(1);
 			erofs_err("failed to get xattr value size of `%s` @ nid %llu",
 				  key, inode->nid | 0ULL);
 			break;
 		}
 		size = ret;
-		value = malloc(size);
-		if (!value) {
-			ret = -ENOMEM;
-			break;
-		}
-		ret = erofs_getxattr(inode, key, value, size);
-		if (ret < 0) {
-			erofs_err("failed to get xattr `%s` @ nid %llu, because of `%s`", key,
-				  inode->nid | 0ULL, erofs_strerror(ret));
-			free(value);
-			break;
+
+		/* Empty xattrs are allowed */
+		if (!size) {
+			value = NULL;
+		} else {
+			value = malloc(size);
+			if (!value) {
+				ret = -ENOMEM;
+				break;
+			}
+
+			ret = erofs_getxattr(inode, key, value, size);
+			if (ret < 0) {
+				erofs_err("failed to get xattr `%s` @ nid %llu, because of `%s`", key,
+					  inode->nid | 0ULL, erofs_strerror(ret));
+				free(value);
+				break;
+			}
 		}
+
 		if (fsckcfg.extract_path)
 			ret = erofs_sys_lsetxattr(fsckcfg.extract_path, key,
 						  value, size);

Thanks,
Gao Xiang

> ---
>  fsck/main.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/fsck/main.c b/fsck/main.c
> index e54c523..9db5ae9 100644
> --- a/fsck/main.c
> +++ b/fsck/main.c
> @@ -458,14 +458,15 @@ static int erofsfsck_dump_xattrs(struct erofs_inode *inode)
>  		size_t size = 0;
>  
>  		ret = erofs_getxattr(inode, key, NULL, 0);
> -		if (ret <= 0) {
> +		if (ret < 0) {
>  			DBG_BUGON(1);
>  			erofs_err("failed to get xattr value size of `%s` @ nid %llu",
>  				  key, inode->nid | 0ULL);
>  			break;
>  		}
>  		size = ret;
> -		value = malloc(size);
> +		/* Empty xattrs are valid */
> +		value = malloc(size ? size : 1);
>  		if (!value) {
>  			ret = -ENOMEM;
>  			break;
> -- 
> 2.43.0
> 
> 


  reply	other threads:[~2026-11-04  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  3:52 [PATCH] erofs-utils: fsck: extract zero-length xattr values Wenyuan Xu
2026-11-04  8:36 ` Gao Xiang [this message]
2026-11-04  9:04   ` Wenyuan Xu

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=aurunz5-1b4visC4@XiangdeMacBook-Pro.local \
    --to=xiang@kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=sereno.xu@deepseek.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