From: Petr Vorel <pvorel@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Qu Wenruo <wqu@suse.com>, Chris Mason <clm@fb.com>,
"kernel-team@lists.ubuntu.com" <kernel-team@lists.ubuntu.com>,
"ltp@lists.linux.it" <ltp@lists.linux.it>,
David Sterba <dsterba@suse.com>,
Filipe Manana <fdmanana@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [LTP] [BUG] btrfs potential failure on 32 core LTP test (fallocate05)
Date: Wed, 30 Jun 2021 13:29:45 +0200 [thread overview]
Message-ID: <YNxVqca+WeQcBmzA@pevik> (raw)
In-Reply-To: <YNxTr43lvviG0GOn@pevik>
Hi all,
...
> > >> Reproduction steps:
> > >> git clone https://github.com/linux-test-project/ltp.git
> > >> cd ltp
> > >> ./build.sh && make install -j8
> > >> cd ../ltp-install
> > >> sudo ./runltp -f syscalls -s fallocate05
NOTE: you can also be a bit faster if you test just single test, see
https://github.com/linux-test-project/ltp#shortcut-to-running-a-single-test
(not compiling and installing whole LTP)
$ cd testcases/kernel/syscalls/fallocate/
$ make -j`nproc`
$ sudo ./fallocate05
> > > This thing keeps trying to test ext2, how do I make it only test btrfs? Thanks,
> > It tests all available file systems, just wait till it gets to btrfs. I
> > don't know how to limit it only to one file system.
> In the future we can add environment variable to specify the only fs to be
> tested. There is LTP_DEV_FS_TYPE, but that does not work when .all_filesystems
> flag is enabled. Thus just patch the file:
NOTE: It detect kernel filesystem support and presence of mkfs.xxx.
Thus other way to limit filesystem is to rename mkfs.xxx of other filesystems
(in case you test LTP from package and don't want / cannot compile and can
modify root filesystem).
Kind regards,
Petr
next prev parent reply other threads:[~2021-06-30 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 17:00 [BUG] btrfs potential failure on 32 core LTP test (fallocate05) Krzysztof Kozlowski
2021-06-29 17:20 ` Josef Bacik
2021-06-29 17:25 ` Krzysztof Kozlowski
2021-06-30 11:21 ` [LTP] " Petr Vorel
2021-06-30 11:29 ` Petr Vorel [this message]
2021-06-29 17:24 ` Josef Bacik
2021-06-29 17:26 ` Krzysztof Kozlowski
2021-06-29 17:28 ` Josef Bacik
2021-06-29 18:06 ` Krzysztof Kozlowski
2021-06-29 18:28 ` Krzysztof Kozlowski
2021-06-29 18:32 ` Josef Bacik
2021-06-30 8:34 ` Krzysztof Kozlowski
2021-06-29 20:14 ` Josef Bacik
2021-06-30 6:52 ` Krzysztof Kozlowski
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=YNxVqca+WeQcBmzA@pevik \
--to=pvorel@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=wqu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox