[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200727105210.GA12348@yuki.lan>
Date: Mon, 27 Jul 2020 12:52:10 +0200
From: Cyril Hrubis <chrubis@...e.cz>
To: Petr Vorel <pvorel@...e.cz>
Cc: kernel test robot <rong.a.chen@...el.com>,
Jens Axboe <axboe@...nel.dk>, Sagi Grimberg <sagi@...mberg.me>,
LKML <linux-kernel@...r.kernel.org>,
Ming Lei <ming.lei@...hat.com>,
Christoph Hellwig <hch@...radead.org>, lkp@...ts.01.org,
Baolin Wang <baolin.wang7@...il.com>,
Christoph Hellwig <hch@....de>, ltp@...ts.linux.it
Subject: Re: [LTP] [blk] 6e6fcbc27e: ltp.fs_fill.fail
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@...e.cz
Powered by blists - more mailing lists