From: "Luís Henriques" <lhenriques@suse.de>
To: fstests@vger.kernel.org
Cc: "Jeff Layton" <jlayton@kernel.org>,
"Xiubo Li" <xiubli@redhat.com>,
ceph-devel@vger.kernel.org, "Luís Henriques" <lhenriques@suse.de>
Subject: [PATCH 1/2] generic/020: adjust max_attrval_size for ceph
Date: Tue, 7 Jun 2022 16:15:12 +0100 [thread overview]
Message-ID: <20220607151513.26347-2-lhenriques@suse.de> (raw)
In-Reply-To: <20220607151513.26347-1-lhenriques@suse.de>
CephFS doesn't had a maximum xattr size. Instead, it imposes a maximum
size for the full set of an inode's xattrs names+values, which by default
is 64K but it can be changed by a cluster admin.
Adjust max_attrval_size so that the test can be executed in this
filesystem.
Signed-off-by: Luís Henriques <lhenriques@suse.de>
---
tests/generic/020 | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/tests/generic/020 b/tests/generic/020
index d8648e96286e..cadfce5f45e3 100755
--- a/tests/generic/020
+++ b/tests/generic/020
@@ -128,15 +128,16 @@ _attr_get_max()
pvfs2)
max_attrval_size=8192
;;
- xfs|udf|9p|ceph)
+ xfs|udf|9p)
max_attrval_size=65536
;;
bcachefs)
max_attrval_size=1024
;;
- nfs)
- # NFS doesn't provide a way to find out the max_attrval_size for
- # the underlying filesystem, so just use the lowest value above.
+ nfs|ceph)
+ # NFS and CephFS don't provide a way to find out the
+ # max_attrval_size for the underlying filesystem, so just use
+ # the lowest value above.
max_attrval_size=1024
;;
*)
next prev parent reply other threads:[~2022-06-07 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 15:15 [PATCH 0/2] Two xattrs-related fixes for ceph Luís Henriques
2022-06-07 15:15 ` Luís Henriques [this message]
2022-06-08 0:16 ` [PATCH 1/2] generic/020: adjust max_attrval_size " Dave Chinner
2022-06-08 9:46 ` Luís Henriques
2022-06-08 21:53 ` Dave Chinner
2022-06-09 9:09 ` Luís Henriques
2022-06-08 8:41 ` Xiubo Li
2022-06-07 15:15 ` [PATCH 2/2] src/attr_replace_test: dynamically adjust the max xattr size Luís Henriques
2022-06-07 15:33 ` Darrick J. Wong
2022-06-07 16:20 ` Luís Henriques
2022-06-07 16:51 ` [PATCH v2] " Luís Henriques
2022-06-08 1:17 ` Xiubo Li
2022-06-08 0:23 ` [PATCH 2/2] " Dave Chinner
2022-06-08 9:57 ` Luís Henriques
2022-06-08 21:59 ` Dave Chinner
2022-06-09 10:32 ` Luís Henriques
2022-06-08 8:50 ` Xiubo Li
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=20220607151513.26347-2-lhenriques@suse.de \
--to=lhenriques@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jlayton@kernel.org \
--cc=xiubli@redhat.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