From: kernel test robot <oliver.sang@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-block@vger.kernel.org>, <oliver.sang@intel.com>
Subject: Re: [PATCH] block: move iostat check into blk_acount_io_start()
Date: Sun, 6 Oct 2024 22:07:33 +0800 [thread overview]
Message-ID: <202410062110.512391df-oliver.sang@intel.com> (raw)
In-Reply-To: <550fc8a0-3461-49ac-879e-32908870f007@kernel.dk>
Hello,
kernel test robot noticed "blktests.block/024.fail" on:
commit: 5b0b8be85f1ca1c11566890f5d4564ee97cf2d41 ("[PATCH] block: move iostat check into blk_acount_io_start()")
url: https://github.com/intel-lab-lkp/linux/commits/Jens-Axboe/block-move-iostat-check-into-blk_acount_io_start/20241003-032648
base: https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-block.git for-next
patch link: https://lore.kernel.org/all/550fc8a0-3461-49ac-879e-32908870f007@kernel.dk/
patch subject: [PATCH] block: move iostat check into blk_acount_io_start()
in testcase: blktests
version: blktests-x86_64-80430af-1_20240910
with following parameters:
disk: 1HDD
test: block-024
compiler: gcc-12
test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202410062110.512391df-oliver.sang@intel.com
2024-10-06 11:02:24 echo block/024
2024-10-06 11:02:24 ./check block/024
block/024 (do I/O faster than a jiffy and check iostats times)
block/024 (do I/O faster than a jiffy and check iostats times) [failed]
runtime ... 2.673s
--- tests/block/024.out 2024-09-10 23:15:59.000000000 +0000
+++ /lkp/benchmarks/blktests/results/nodev/block/024.out.bad 2024-10-06 11:02:27.595709543 +0000
@@ -1,10 +1,10 @@
Running block/024
read 0 s
write 0 s
-read 1 s
+read 70000 s
write 0 s
-read 1 s
...
(Run 'diff -u tests/block/024.out /lkp/benchmarks/blktests/results/nodev/block/024.out.bad' to see the entire diff)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241006/202410062110.512391df-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-10-06 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 19:26 [PATCH] block: move iostat check into blk_acount_io_start() Jens Axboe
2024-10-02 19:40 ` Keith Busch
2024-10-03 8:44 ` Anuj gupta
2024-10-03 13:09 ` Christoph Hellwig
2024-10-03 13:19 ` Jens Axboe
2024-10-06 14:07 ` kernel test robot [this message]
2024-10-06 21:11 ` Jens Axboe
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=202410062110.512391df-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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