From: Ming Lei <ming.lei@redhat.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: kernel test robot <rong.a.chen@intel.com>,
Jens Axboe <axboe@kernel.dk>, Sagi Grimberg <sagi@grimberg.me>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
lkp@lists.01.org, Baolin Wang <baolin.wang7@gmail.com>,
Christoph Hellwig <hch@lst.de>,
ltp@lists.linux.it
Subject: Re: [LTP] [blk] 6e6fcbc27e: ltp.fs_fill.fail
Date: Mon, 27 Jul 2020 23:14:16 +0800 [thread overview]
Message-ID: <20200727151416.GA1298062@T590> (raw)
In-Reply-To: <20200727093156.GA29739@dell5510>
On Mon, Jul 27, 2020 at 11:31:56AM +0200, Petr Vorel wrote:
> Hi,
>
> > FYI, we noticed the following commit (built with gcc-9):
>
> > commit: 6e6fcbc27e7788af54139c53537395d95560f2ef ("blk-mq: support batching dispatch in case of io")
> > https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-block.git for-5.9/drivers
>
>
> > in testcase: ltp
> > with following parameters:
>
> > disk: 1HDD
> > fs: ext4
> > test: fs-03
>
> > test-description: The LTP testsuite contains a collection of tools for testing the Linux kernel and related features.
> > test-url: http://linux-test-project.github.io/
>
>
> > on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
>
> > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
> ...
> > tst_test.c:1308: INFO: Testing on vfat
> > tst_mkfs.c:90: INFO: Formatting /dev/loop0 with vfat opts='' extra opts=''
> > tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
> > fs_fill.c:103: INFO: Running 10 writer threads
> > Test timeouted, sending SIGKILL!
> > Test timeouted, sending SIGKILL!
> > Test timeouted, sending SIGKILL!
> > Test timeouted, sending SIGKILL!
> > Test timeouted, sending SIGKILL!
> > Test timeouted, sending SIGKILL!
> The only "error" I found is that fs_fill test timeouted on vfat. That might
> indicate some problems. Note, for slow machines, there is LTP_TIMEOUT_MUL
> https://github.com/linux-test-project/ltp/wiki/User-Guidelines#1-library-environment-variables
I have run fs_fill test for a while, and can't reproduce it, and I am
sure vfat is covered.
Thanks,
Ming
next prev parent reply other threads:[~2020-07-27 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 7:55 [blk] 6e6fcbc27e: ltp.fs_fill.fail kernel test robot
2020-07-26 8:42 ` Ming Lei
2020-07-27 9:31 ` [LTP] " Petr Vorel
2020-07-27 10:52 ` Cyril Hrubis
2020-07-27 15:14 ` Ming Lei [this message]
2020-08-07 8:22 ` Ming Lei
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=20200727151416.GA1298062@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=baolin.wang7@gmail.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=rong.a.chen@intel.com \
--cc=sagi@grimberg.me \
/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