From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>,
ltp@lists.linux.it, Li Wang <liwang@redhat.com>,
Jan Stancek <jstancek@redhat.com>,
Andrea Cervesato <andrea.cervesato@suse.de>,
Jan Polensky <japo@linux.ibm.com>
Subject: Re: [LTP] [PATCH] lib: LTP_SINGLE_FS_TYPE fix fuse blacklist
Date: Thu, 22 May 2025 21:57:07 +0200 [thread overview]
Message-ID: <20250522195707.GB26060@pevik> (raw)
In-Reply-To: <20250522192612.GA26060@pevik>
Hi Cyril, all,
...
> > > Could we clearly define what we expect from LTP_SINGLE_FS_TYPE?
> > > FYI I put links to the discussion in the ticket
> > > https://github.com/linux-test-project/ltp/issues/1242
> > > I understand the wish to use LTP_SINGLE_FS_TYPE for a proper testing. If that
> > > requires to respect .skip_filesystems, but
> > > 1) it should be done for all filesystems
> > > 2) we should have another variable to allow to force the user defined
> > > filesystem, e.g.
> > > LTP_SINGLE_FS_TYPE=ntfs LTP_SINGLE_FS_TYPE_FORCE_FS=1
> > What about LTP_FORCE_SINGLE_FS_TYPE=ntfs that would do the same as
> > LTP_SINGLE_FS_TYPE=ntfs but would disable the skiplist?
Also, what if both are set? Should it be mutually exclusive?
Kind regards,
Petr
> +1, it should go to the release.
> But please update also doc doc/users/setup_tests.rst + -h help in lib/tst_test.c
> and testcases/lib/tst_test.sh (variable will of course affect both).
> Kind regards,
> Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-05-22 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 9:53 [LTP] [PATCH] lib: LTP_SINGLE_FS_TYPE fix fuse blacklist Cyril Hrubis
2025-05-22 16:14 ` Jan Polensky
2025-05-22 17:31 ` Petr Vorel
2025-05-22 17:47 ` Cyril Hrubis
2025-05-22 19:26 ` Petr Vorel
2025-05-22 19:57 ` Petr Vorel [this message]
2025-05-26 10:09 ` 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=20250522195707.GB26060@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.de \
--cc=chrubis@suse.cz \
--cc=japo@linux.ibm.com \
--cc=jstancek@redhat.com \
--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 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.