From: David Disseldorp <ddiss@suse.de>
To: "Luís Henriques" <lhenriques@suse.de>
Cc: fstests@vger.kernel.org, Zorro Lang <zlang@redhat.com>,
Dave Chinner <david@fromorbit.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Jeff Layton <jlayton@kernel.org>, Xiubo Li <xiubli@redhat.com>,
ceph-devel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] generic/486: adjust the max xattr size
Date: Mon, 13 Jun 2022 14:24:44 +0200 [thread overview]
Message-ID: <20220613142444.3276dfa8@suse.de> (raw)
In-Reply-To: <20220613113142.4338-3-lhenriques@suse.de>
On Mon, 13 Jun 2022 12:31:42 +0100, Luís Henriques wrote:
> CephFS doesn't have a maximum xattr size. Instead, it imposes a maximum
> size for the full set of xattrs names+values, which by default is 64K. And
> since it reports 4M as the blocksize (the default ceph object size),
> generic/486 will fail in ceph because the XATTR_SIZE_MAX value can't be used
> in attr_replace_test.
>
> The fix is to add a new argument to the test so that the max size can be
> passed in instead of trying to auto-probe a value for it.
>
> Signed-off-by: Luís Henriques <lhenriques@suse.de>
> ---
> src/attr_replace_test.c | 30 ++++++++++++++++++++++++++----
> tests/generic/486 | 11 ++++++++++-
> 2 files changed, 36 insertions(+), 5 deletions(-)
>
> diff --git a/src/attr_replace_test.c b/src/attr_replace_test.c
> index cca8dcf8ff60..1218e7264c8f 100644
> --- a/src/attr_replace_test.c
> +++ b/src/attr_replace_test.c
> @@ -20,19 +20,41 @@ exit(1); } while (0)
> fprintf(stderr, __VA_ARGS__); exit (1); \
> } while (0)
>
> +void usage(char *progname)
> +{
> + fail("usage: %s [-m max_attr_size] <file>\n", progname);
> +}
> +
> int main(int argc, char *argv[])
> {
> int ret;
> int fd;
> + int c;
> char *path;
> char *name = "user.world";
> char *value;
> struct stat sbuf;
> size_t size = sizeof(value);
> + size_t maxsize = XATTR_SIZE_MAX;
> +
> + while ((c = getopt(argc, argv, "m:")) != -1) {
> + char *endp;
> +
> + switch (c) {
> + case 'm':
> + maxsize = strtoul(optarg, &endp, 0);
> + if (*endp || (maxsize > XATTR_SIZE_MAX))
> + fail("Invalid 'max_attr_size' value\n");
> + break;
> + default:
> + usage(argv[0]);
> + }
> + }
>
> - if (argc != 2)
> - fail("Usage: %s <file>\n", argv[0]);
> - path = argv[1];
> + if (optind == argc - 1)
> + path = argv[optind];
> + else
> + usage(argv[0]);
>
> fd = open(path, O_RDWR | O_CREAT, S_IRUSR | S_IWUSR);
> if (fd < 0) die();
> @@ -46,7 +68,7 @@ int main(int argc, char *argv[])
> size = sbuf.st_blksize * 3 / 4;
> if (!size)
> fail("Invalid st_blksize(%ld)\n", sbuf.st_blksize);
> - size = MIN(size, XATTR_SIZE_MAX);
> + size = MIN(size, maxsize);
> value = malloc(size);
> if (!value)
> fail("Failed to allocate memory\n");
> diff --git a/tests/generic/486 b/tests/generic/486
> index 7de198f93a71..7dbfcb9835d9 100755
> --- a/tests/generic/486
> +++ b/tests/generic/486
> @@ -41,7 +41,16 @@ filter_attr_output() {
> sed -e 's/has a [0-9]* byte value/has a NNNN byte value/g'
> }
>
> -$here/src/attr_replace_test $SCRATCH_MNT/hello
> +max_attr_size=65536
> +
> +# attr_replace_test can't easily auto-probe the attr size for ceph because:
> +# - ceph imposes a maximum value for the total xattr names+values, and
> +# - ceph reports the 'object size' in the block size, which is, by default, much
> +# larger than XATTR_SIZE_MAX (4M > 64k)
> +# Hence, we need to provide it with a maximum size.
> +[ "$FSTYP" = "ceph" ] && max_attr_size=65000
> +
> +$here/src/attr_replace_test -m $max_attr_size $SCRATCH_MNT/hello
> $ATTR_PROG -l $SCRATCH_MNT/hello >>$seqres.full 2>&1
> $ATTR_PROG -l $SCRATCH_MNT/hello | filter_attr_output
Looks okay as an alternative to going through a 73aa648c
("generic/020: move MAX_ATTRS and MAX_ATTRVAL_SIZE logic") revert.
Reviewed-by: David Disseldorp <ddiss@suse.de>
next prev parent reply other threads:[~2022-06-13 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 11:31 [PATCH v3 0/2] Two xattrs-related fixes for ceph Luís Henriques
2022-06-13 11:31 ` [PATCH v3 1/2] generic/020: adjust max_attrval_size " Luís Henriques
2022-06-13 12:21 ` David Disseldorp
2022-06-13 11:31 ` [PATCH v3 2/2] generic/486: adjust the max xattr size Luís Henriques
2022-06-13 12:24 ` David Disseldorp [this message]
2022-06-14 9:22 ` [PATCH v3 0/2] Two xattrs-related fixes for ceph 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=20220613142444.3276dfa8@suse.de \
--to=ddiss@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jlayton@kernel.org \
--cc=lhenriques@suse.de \
--cc=xiubli@redhat.com \
--cc=zlang@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