From: Josef Bacik <josef@toxicpanda.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"kernel-team@lists.ubuntu.com" <kernel-team@lists.ubuntu.com>,
"ltp@lists.linux.it" <ltp@lists.linux.it>,
Qu Wenruo <wqu@suse.com>, Filipe Manana <fdmanana@suse.com>
Subject: Re: [BUG] btrfs potential failure on 32 core LTP test (fallocate05)
Date: Tue, 29 Jun 2021 13:20:40 -0400 [thread overview]
Message-ID: <e4c71c01-ed70-10a6-be4d-11966d1fcb75@toxicpanda.com> (raw)
In-Reply-To: <a3b42abc-6996-ab06-ea9f-238e7c6f08d7@canonical.com>
On 6/29/21 1:00 PM, Krzysztof Kozlowski wrote:
> Dear BTRFS folks,
>
> I am hitting a potential regression of btrfs, visible only with
> fallocate05 test from LTP (Linux Test Project) only on 32+ core Azure
> instances (x86_64).
>
> Tested:
> v5.8 (Ubuntu with our stable patches): PASS
> v5.11 (Ubuntu with our stable patches): FAIL
> v5.13 mainline: FAIL
>
> PASS means test passes on all instances
> FAIL means test passes on other instance types (e.g. 4 or 16 core) but
> fails on 32 and 64 core instances (did not test higher),
> e.g.: Standard_F32s_v2, Standard_F64s_v2, Standard_D32s_v3,
> Standard_E32s_v3
>
> 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
>
This thing keeps trying to test ext2, how do I make it only test btrfs? Thanks,
Josef
next prev parent reply other threads:[~2021-06-29 17:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 17:00 Krzysztof Kozlowski
2021-06-29 17:20 ` Josef Bacik [this message]
2021-06-29 17:25 ` Krzysztof Kozlowski
2021-06-30 11:21 ` [LTP] " Petr Vorel
2021-06-30 11:29 ` Petr Vorel
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=e4c71c01-ed70-10a6-be4d-11966d1fcb75@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=krzysztof.kozlowski@canonical.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
all inboxes | Powered by JetHome®