public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH] Delete New ext4 features tests and ffsb tool
Date: Thu, 24 Oct 2019 13:05:02 +0200	[thread overview]
Message-ID: <20191024110502.GA27782@rei.lan> (raw)
In-Reply-To: <20191024090753.16789-1-pvorel@suse.cz>

Hi!
> The main reason is that these tests [1] (contributed in 2009)
> are mostly outdated and irrelevant. According to Theodore Y. Tso [2]
> and Jan Kara [3] the only partly valid tests are
> ext4_nsec_timestamps_test.sh and ext4_subdir_limit_test.sh,
> but even these would be better to migrate to xfstests,
> which Yong Sun is planning to do.
> 
> Also, some of the tests weren't in any runtest file anyway
> (ext4-alloc-test.sh, ext4_inode_version_test.sh,
> ext4_journal_checksum.sh, ext4_online_defrag_test.sh)
> 
> ffsb tool was used only in these New ext4 features tests.
> 
> [1] http://ext4.wiki.kernel.org/index.php/New_ext4_features
> [2] https://marc.info/?l=linux-fsdevel&m=157187153211649&w=2
> [3] https://marc.info/?l=linux-ext4&m=157190318618555&w=2
> 
> Closes: #560

Acked.

The ffsb adds quite a bit of complexity to the LTP build with a very
little added value. As far as the meaningful parts of the ext4 suite
would be migrated to xfstests everyone should be happy about this.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2019-10-24 11:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24  9:07 [LTP] [RFC PATCH] Delete New ext4 features tests and ffsb tool Petr Vorel
2019-10-24 11:05 ` Cyril Hrubis [this message]
2019-10-24 12:26   ` Petr Vorel

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=20191024110502.GA27782@rei.lan \
    --to=chrubis@suse.cz \
    --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