public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] tst_supported_fs: Implement checking paths against skiplist
Date: Thu, 22 Sep 2022 11:02:21 +0200	[thread overview]
Message-ID: <YywknXj4nL48PaR6@pevik> (raw)
In-Reply-To: <CAEemH2eoxjDha9Ldu9shqO6MUUFfvT3dkFExAHGyH-38E5drVg@mail.gmail.com>

Hi all,

> > Although the tst_fs_type_name() functions could use some improvements,
> > e.g. ext4 must be specified in skiplist as "ext2/ext3/ext4" to get properly

> Yes, that's true, we need to make it keep consistent with two
> skipping ways. Otherwise below test output "ext2/ext3/ext4"
> looks like a bit mess to remember.

> Better going with a single FS for matching (i.e. "ext4" for both fs_type
> and '-d path').
> But we can solve this in a separate patch later.

> $ df -T . | tail -1 | awk '{print $2}'
> ext4

> $ ./tst_supported_fs -s "ext4" ext4
> tst_supported_fs.c:135: TCONF: ext4 is skipped
> $ echo $?
> 32

> $ ./tst_supported_fs -s "ext4" -d .
> tst_supported_fs.c:137: TINFO: ext2/ext3/ext4 is not skipped
> $ echo $?
> 0

> $ ./tst_supported_fs -s "ext2/ext3/ext4" -d .
> tst_supported_fs.c:135: TCONF: ext2/ext3/ext4 is skipped
> $ echo $?
> 32

The same problem is for .skip_filesystems on tests which does not use
.all_filesystems. We only haven't noticed, because there was no reason to skip
ext[234] so far. I'm looking into this.

BTW .skip_filesystems without .all_filesystems have other problems, e.g. using
filesystems which aren't in fs_type_whitelist[] array (e.g. ramfs, nfs).
That'd be nice to fix after the release.

Kind regards,
Petr

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

  parent reply	other threads:[~2022-09-22  9:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 15:50 [LTP] [PATCH] tst_supported_fs: Implement checking paths against skiplist Martin Doucha
2022-09-22  4:16 ` Li Wang
2022-09-22  8:14   ` Martin Doucha
2022-09-22  8:43     ` Petr Vorel
2022-09-22  9:08       ` Li Wang
2022-09-22  9:56         ` Petr Vorel
2022-09-22  9:02   ` Petr Vorel [this message]
2022-09-22  9:24     ` Li Wang
2022-09-22 10:40       ` Petr Vorel
2022-09-22 10:55         ` Cyril Hrubis
2022-09-22 10:57           ` Martin Doucha
2022-09-22 11:20             ` Petr Vorel
2022-09-22 14:42               ` Cyril Hrubis
2022-09-22 20:22                 ` Petr Vorel
2022-09-22  8:56 ` Petr Vorel
2022-09-22 20:26 ` Petr Vorel
2022-09-23 10:00 ` Petr Vorel
2022-09-26  7:48   ` Petr Vorel
2022-09-23 15:17 ` Cyril Hrubis

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=YywknXj4nL48PaR6@pevik \
    --to=pvorel@suse.cz \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    /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