All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Avinesh Kumar <akumar@suse.de>
Cc: Richard Palethorpe <rpalethorpe@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] statvfs01: Convert to new LTP API
Date: Wed, 30 Nov 2022 09:52:20 +0100	[thread overview]
Message-ID: <Y4cZxK/SqTtpQb07@pevik> (raw)
In-Reply-To: <20221130070500.28664-1-akumar@suse.de>

Hi Avinesh,

> Removed the TINFO statements,
> Added a validation of statvfs.f_namemax field by trying to create
> files of valid and invalid length names.
Very nice rewrite, thanks for adding this veryfication.
It'd be nice to update this in docparse description.

> +
> +/*\
> + * [Description]
> + *
> + * Verify that statvfs() executes successfully for all
> + * available filesystems.
e.g.:
Verify that statvfs() executes successfully for all
available filesystems. Verify statvfs.f_namemax field
by trying to create files of valid and invalid length names.

I can merge it with this change.

Reviewed-by: Petr Vorel <pvorel@suse.cz>

...
> +static struct tst_test test = {
> +	.test_all = run,
> +	.setup = setup,
> +	.needs_root = 1,
> +	.mount_device = 1,
> +	.mntpoint = MNT_POINT,
> +	.all_filesystems = 1,
> +	.skip_filesystems = (const char *const[]) {
> +		"vfat",
> +		"exfat",
I was looking what's wrong with vfat and exfat.
statvfs.f_namemax returns 1530, which is obviously too long, thus valid_fname
obviously returns ENAMETOOLONG (36). Tested on 6.1.0-rc6-1.g4c01546-default.
I wonder why, isn't that a bug?

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-11-30  8:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 11:42 [LTP] [PATCH] statvfs01: Convert to new LTP API Avinesh Kumar
2022-11-25  2:18 ` Li Wang
2022-11-29 10:58   ` Richard Palethorpe
2022-11-30  7:05     ` [LTP] [PATCH v2] " Avinesh Kumar
2022-11-30  8:52       ` Petr Vorel [this message]
2022-11-30  9:50         ` Petr Vorel
2022-12-01  5:16           ` Li Wang
2022-12-01  9:34             ` Richard Palethorpe
2022-12-02  9:20               ` Petr Vorel
2022-12-01  8:51           ` Avinesh Kumar
2022-12-01  9:17             ` Li Wang
2022-12-01 10:45               ` Petr Vorel
2022-12-01 11:04                 ` Avinesh Kumar
2022-11-30  7:20     ` [LTP] [PATCH] " Li Wang
2022-12-01  6:00       ` Li Wang

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=Y4cZxK/SqTtpQb07@pevik \
    --to=pvorel@suse.cz \
    --cc=akumar@suse.de \
    --cc=ltp@lists.linux.it \
    --cc=rpalethorpe@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.