Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: a1e09b03e6f5c1d713c88259909137c0fd264ede ("f2fs: use iomap for direct I/O")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: ltp
version: ltp-x86_64-14c1f76-1_20211221
with following parameters:
disk: 1HDD
fs: f2fs
test: ltp-aiodio.part2
ucode: 0x21
test-description: The LTP testsuite contains a collection of tools for testing the Linux kernel and related features.
test-url: http://linux-test-project.github.io/
on test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz with 8G memory
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <[email protected]>
[ 106.307903][ T324] tag=ADSP024 stime=1640375440
[ 106.307911][ T324]
[ 106.309407][ T324] cmdline="aiodio_sparse -i 4 -a 8k -w 1024k -s 4096k -n 6"
[ 106.309415][ T324]
[ 106.309855][ T324] contacts=""
[ 106.309862][ T324]
[ 106.310269][ T324] analysis=exit
[ 106.310276][ T324]
[ 106.310820][ T324] <<<test_output>>>
[ 106.310827][ T324]
[ 106.312502][ T324] non zero buffer at buf[0] => 0xffffffaa,ffffffaa,ffffffaa,ffffffaa
[ 106.312510][ T324]
[ 106.313451][ T324] non-zero read at offset 3915776
[ 106.313459][ T324]
[ 106.314764][ T324] aiodio_sparse 0 TINFO : Dirtying free blocks
[ 106.314772][ T324]
[ 106.316062][ T324] aiodio_sparse 0 TINFO : Starting I/O tests
[ 106.316069][ T324]
[ 106.317884][ T324] non zero buffer at buf[0] => 0xffffffaa,ffffffaa,ffffffaa,ffffffaa
[ 106.317893][ T324]
[ 106.318836][ T324] non-zero read at offset 4034560
[ 106.318844][ T324]
[ 106.320167][ T324] aiodio_sparse 0 TINFO : Dirtying free blocks
[ 106.320175][ T324]
[ 106.321599][ T324] aiodio_sparse 0 TINFO : Starting I/O tests
[ 106.321607][ T324]
[ 106.323179][ T324] aiodio_sparse 0 TINFO : Dirtying free blocks
[ 106.323192][ T324]
[ 106.324706][ T324] aiodio_sparse 0 TINFO : Starting I/O tests
[ 106.324715][ T324]
[ 106.326305][ T324] aiodio_sparse 0 TINFO : Killing childrens(s)
[ 106.326313][ T324]
[ 106.328815][ T324] aiodio_sparse 1 TFAIL : aiodio_sparse.c:309: 2 children(s) exited abnormally
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.
---
0DAY/LKP+ Test Infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/[email protected] Intel Corporation
Thanks,
Oliver Sang
On Sun, Dec 26, 2021 at 09:28:52PM +0800, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: a1e09b03e6f5c1d713c88259909137c0fd264ede ("f2fs: use iomap for direct I/O")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> in testcase: ltp
> version: ltp-x86_64-14c1f76-1_20211221
> with following parameters:
>
> disk: 1HDD
> fs: f2fs
> test: ltp-aiodio.part2
> ucode: 0x21
>
This is caused by an f2fs bug where it exposes DIO-allocated blocks to users
before they have been initialized. This test actually fails both before and
after my commit "f2fs: use iomap for direct I/O". It is nondeterministic, which
is why it may have appeared to be a regression.
I'll start a separate discussion on linux-f2fs-devel about this, since this
thread has too many irrelevant mailing lists and this has been discussed before.
- Eric