public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it, Zorro Lang <zlang@kernel.org>,
	linux-btrfs@vger.kernel.org
Subject: Re: [LTP] [PATCH 1/3] ioctl_ficlone02.c: set all_filesystems to zero
Date: Wed, 11 Dec 2024 13:08:59 +0100	[thread overview]
Message-ID: <Z1mA2wzjW0hpQxUH@yuki.lan> (raw)
In-Reply-To: <20241209061416.GB180329@pevik>

Hi!
> Well, "Testing only" in the help (-h) was added there to suggest it's for
> testing/debugging LTP, not a production testing. But newer mind, I'll implement
> Cyril's suggestion, real usage justify it. + I'll add LTP_FORCE_SINGLE_FS_TYPE.
> 
> We could allow more filesystems, e.g.  instead of running LTP few times with
> different LTP_SINGLE_FS_TYPE value: e.g.
> 
> for fs in ext4 xfs btrfs; do LTP_SINGLE_FS_TYPE=fs ioctl_ficlone02; done
> 
> we could introduce support for particular filesystems
> LTP_FILESYSTEMS="ext4,xfs,btrfs" ioctl_ficlone02

That is stil not equivalent if you run it with a whole LTP. We would
have to run each test that uses device for all LTP_FILESYSTEMS, since
many of the testcases does use device but does not use .all_filesystems.

So all in all I think that LTP_SINGLE_FS_TYPE is good enough solution.

Or we can try to rething the whole thing, but it's getting quite
complicated with all the options we have.

-- 
Cyril Hrubis
chrubis@suse.cz

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

  parent reply	other threads:[~2024-12-11 12:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-01  9:36 [LTP] [PATCH 0/3] LTP random fixes for xfs and btrfs Zorro Lang via ltp
2024-12-01  9:36 ` [LTP] [PATCH 1/3] ioctl_ficlone02.c: set all_filesystems to zero Zorro Lang via ltp
2024-12-02 13:36   ` Cyril Hrubis
2024-12-02 13:59     ` Cyril Hrubis
2024-12-02 14:42       ` Petr Vorel
2024-12-02 15:23         ` Cyril Hrubis
2024-12-03  4:53           ` Petr Vorel
2024-12-03  7:58             ` Cyril Hrubis
2024-12-03  9:24               ` Petr Vorel
2024-12-09  5:53         ` Zorro Lang via ltp
2024-12-09  6:14           ` Petr Vorel
2024-12-09  9:49             ` Zorro Lang via ltp
2024-12-09 10:42               ` Petr Vorel
2024-12-09 11:34               ` Petr Vorel
2024-12-11 12:08             ` Cyril Hrubis [this message]
2024-12-11 19:40               ` Petr Vorel
2024-12-01  9:36 ` [LTP] [PATCH 2/3] stat04+lstat03: fix bad blocksize mkfs option for xfs Zorro Lang via ltp
2024-12-02 13:56   ` Cyril Hrubis
2024-12-01  9:36 ` [LTP] [PATCH 3/3] stat04+lstat03: skip test on btrfs Zorro Lang via ltp
2024-12-02 13:55   ` Cyril Hrubis
2024-12-01  9:55 ` [LTP] [PATCH 0/3] LTP random fixes for xfs and btrfs Qu Wenruo via ltp
2024-12-03 16:22   ` David Sterba

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=Z1mA2wzjW0hpQxUH@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    --cc=zlang@kernel.org \
    /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