Greeting,
Please note this report is for the v4 patch at
https://lore.kernel.org/r/167305163159.1521586.9460968250704377087.stgit@warthog.procyon.org.uk/
Since v5 has been posted, this report is for your reference only.
We noticed blktests.zbd/(003/004).fail and blktests.loop/(002/004).fail due to commit (built with gcc-11):
commit: 64ea9d6c5f473c29c5de97abaa697856db90fef7 ("iov_iter: Use IOCB/IOMAP_WRITE if available rather than iterator direction")
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git iov-extract
in testcase: blktests
version: blktests-x86_64-b35866f-1_20221206
on test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) with 32G memory
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
zbd/003 => nullb1 (reset sequential required zones) [failed]
runtime ... 0.114s
--- tests/zbd/003.out 2022-12-06 16:53:11.000000000 +0000
+++ /lkp/benchmarks/blktests/results/nullb1/zbd/003.out.bad 2023-01-13 08:00:28.524999773 +0000
@@ -1,2 +1,2 @@
Running zbd/003
-Test complete
+Unexpected write poiter position in zone 0 wp: 0
zbd/004 => nullb1 (write split across sequential zones) [failed]
runtime ... 0.264s
--- tests/zbd/004.out 2022-12-06 16:53:11.000000000 +0000
+++ /lkp/benchmarks/blktests/results/nullb1/zbd/004.out.bad 2023-01-12 11:01:10.806858146 +0000
@@ -1,2 +1,2 @@
Running zbd/004
-Test complete
+Zone 0 condition is not FULL cond: EMPTY
loop/002 (try various loop device block sizes) [failed]
runtime ... 0.234s
--- tests/loop/002.out 2022-12-06 16:53:11.000000000 +0000
+++ /lkp/benchmarks/blktests/results/nodev/loop/002.out.bad 2023-01-13 14:24:10.596748767 +0000
@@ -2,18 +2,18 @@
Checking default block size
512
Setting block size to 4096
-769bd186841c10e5b1106b55986206c0e87fc05a7f565fdee01b5abcaff6ae78 -
+ad7facb2586fc6e966c004d7d1d16b024f5805ff7cb47c7a85dabd8b48892ca7 -
4096
Setting block size to 2048
...
(Run 'diff -u tests/loop/002.out /lkp/benchmarks/blktests/results/nodev/loop/002.out.bad' to see the entire diff)
loop/004 (combine loop direct I/O mode and a custom block size) [failed]
runtime ... 0.636s
--- tests/loop/004.out 2022-12-06 16:53:11.000000000 +0000
+++ /lkp/benchmarks/blktests/results/nodev/loop/004.out.bad 2023-01-13 14:35:07.645643053 +0000
@@ -1,4 +1,4 @@
Running loop/004
1
-769bd186841c10e5b1106b55986206c0e87fc05a7f565fdee01b5abcaff6ae78 -
+ad7facb2586fc6e966c004d7d1d16b024f5805ff7cb47c7a85dabd8b48892ca7 -
Test complete
If you fix the issue, kindly add following tag
| Reported-by: kernel test robot <[email protected]>
| Link: https://lore.kernel.org/oe-lkp/[email protected]
To reproduce:
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
sudo bin/lkp install job.yaml # job file is attached in this email
bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run
sudo bin/lkp run generated-yaml-file
# if come across any failure that blocks the test,
# please remove ~/.lkp and /lkp dir to run from a clean state.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests