From: kernel test robot <oliver.sang@intel.com>
To: Joel Granados <joel.granados@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
Kees Cook <kees@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Joel Granados <joel.granados@kernel.org>, <oliver.sang@intel.com>
Subject: Re: [PATCH 3/9] sysctl: Generate do_proc_doulongvec_minmax with do_proc_dotypevec macro
Date: Mon, 29 Dec 2025 15:17:58 +0800 [thread overview]
Message-ID: <202512291555.395cc7b0-lkp@intel.com> (raw)
In-Reply-To: <20251219-jag-dovec_consolidate-v1-3-1413b92c6040@kernel.org>
Hello,
kernel test robot noticed "blktests.block/020.fail" on:
commit: 216729bf72d98eca7a48326bb17b577c3fde9634 ("[PATCH 3/9] sysctl: Generate do_proc_doulongvec_minmax with do_proc_dotypevec macro")
url: https://github.com/intel-lab-lkp/linux/commits/Joel-Granados/sysctl-Move-default-converter-assignment-out-of-do_proc_dointvec/20251219-202253
patch link: https://lore.kernel.org/all/20251219-jag-dovec_consolidate-v1-3-1413b92c6040@kernel.org/
patch subject: [PATCH 3/9] sysctl: Generate do_proc_doulongvec_minmax with do_proc_dotypevec macro
in testcase: blktests
version: blktests-x86_64-b1b99d1-1_20251223
with following parameters:
disk: 1HDD
test: block-020
config: x86_64-rhel-9.4-func
compiler: gcc-14
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/202512291555.395cc7b0-lkp@intel.com
2025-12-26 15:49:33 cd /lkp/benchmarks/blktests
2025-12-26 15:49:33 echo block/020
2025-12-26 15:49:33 ./check block/020
block/020 (run null-blk on different schedulers with only one hardware tag)
block/020 (run null-blk on different schedulers with only one hardware tag) [failed]
runtime ... 42.071s
--- tests/block/020.out 2025-12-23 16:47:43.000000000 +0000
+++ /lkp/benchmarks/blktests/results/nodev/block/020.out.bad 2025-12-26 15:50:16.434082831 +0000
@@ -1,2 +1,10 @@
Running block/020
+iodepth: min value out of range: -16384 (1 min)
+_fio_perf: too many terse lines
+iodepth: min value out of range: -16384 (1 min)
+_fio_perf: too many terse lines
+iodepth: min value out of range: -16384 (1 min)
+_fio_perf: too many terse lines
...
(Run 'diff -u tests/block/020.out /lkp/benchmarks/blktests/results/nodev/block/020.out.bad' to see the entire diff)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251229/202512291555.395cc7b0-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2025-12-29 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251219-jag-dovec_consolidate-v1-3-1413b92c6040@kernel.org>
2025-12-29 7:17 ` kernel test robot [this message]
2026-01-01 12:56 ` [PATCH 3/9] sysctl: Generate do_proc_doulongvec_minmax with do_proc_dotypevec macro Joel Granados
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=202512291555.395cc7b0-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
/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