Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Weizhao Ouyang <o451686892@gmail.com>
To: linux-erofs@lists.ozlabs.org
Cc: Weizhao Ouyang <o451686892@gmail.com>
Subject: [PATCH] erofs-utils: xattr: skip NFSv4 xattrs building
Date: Wed, 19 Apr 2023 16:56:09 +0800	[thread overview]
Message-ID: <20230419085609.6601-1-o451686892@gmail.com> (raw)

Skip NFSv4 xattrs(system.nfs4_acl/dacl/sacl) to avoid ENODATA error when
compiling AOSP on NFSv4 servers.

Signed-off-by: Weizhao Ouyang <o451686892@gmail.com>
---
 lib/xattr.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/lib/xattr.c b/lib/xattr.c
index 6034e7b6b4eb..748bf2e13408 100644
--- a/lib/xattr.c
+++ b/lib/xattr.c
@@ -288,6 +288,9 @@ static bool erofs_is_skipped_xattr(const char *key)
 	if (cfg.sehnd && !strcmp(key, XATTR_SECURITY_PREFIX "selinux"))
 		return true;
 #endif
+	/* skip xattr nfs4_acl/dacl/sacl */
+	if (!strncmp(key, "system.nfs4_", strlen("system.nfs4_")))
+		return true;
 	return false;
 }
 
-- 
2.25.1


             reply	other threads:[~2023-04-19  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19  8:56 Weizhao Ouyang [this message]
2023-04-19  9:03 ` [PATCH] erofs-utils: xattr: skip NFSv4 xattrs building Gao Xiang
2023-04-19  9:04   ` Gao Xiang
2023-04-19  9:54     ` Weizhao Ouyang

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=20230419085609.6601-1-o451686892@gmail.com \
    --to=o451686892@gmail.com \
    --cc=linux-erofs@lists.ozlabs.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