From: Cyril Hrubis <chrubis@suse.cz>
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>,
Ming Lei <ming.lei@redhat.com>,
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 12:52:10 +0200 [thread overview]
Message-ID: <20200727105210.GA12348@yuki.lan> (raw)
In-Reply-To: <20200727093156.GA29739@dell5510>
Hi!
> > 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
Actually you had removed the most important part, it not only timeouted
but the process ended up stuck in kernel and could not be killed. So
this looks like deadlock somewhere in filesystem code.
--
Cyril Hrubis
chrubis@suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [blk] 6e6fcbc27e: ltp.fs_fill.fail
Date: Mon, 27 Jul 2020 12:52:10 +0200 [thread overview]
Message-ID: <20200727105210.GA12348@yuki.lan> (raw)
In-Reply-To: <20200727093156.GA29739@dell5510>
Hi!
> > 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
Actually you had removed the most important part, it not only timeouted
but the process ended up stuck in kernel and could not be killed. So
this looks like deadlock somewhere in filesystem code.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-07-27 10:51 UTC|newest]
Thread overview: 13+ 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 7:55 ` [LTP] " kernel test robot
2020-07-26 8:42 ` Ming Lei
2020-07-26 8:42 ` [LTP] " Ming Lei
2020-07-27 9:31 ` Petr Vorel
2020-07-27 9:31 ` Petr Vorel
2020-07-27 10:52 ` Cyril Hrubis [this message]
2020-07-27 10:52 ` Cyril Hrubis
2020-07-27 15:14 ` Ming Lei
2020-07-27 15:14 ` Ming Lei
2020-08-07 8:22 ` Ming Lei
2020-08-07 8:22 ` Ming Lei
2020-08-07 8:22 ` [LTP] " 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=20200727105210.GA12348@yuki.lan \
--to=chrubis@suse.cz \
--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=ming.lei@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.