On Mar 01, 2024 / 15:49, Yi Zhang wrote: > On Wed, Feb 28, 2024 at 8:08 PM Yi Zhang <yi.zh...@redhat.com> wrote: > > > > On Wed, Feb 28, 2024 at 7:09 PM Shinichiro Kawasaki > > <shinichiro.kawas...@wdc.com> wrote: > > > > > > On Feb 19, 2024 / 00:58, Yi Zhang wrote: > > > > Hello > > > > I reproduced this issue on the latest linux-block/for-next, please > > > > help check it and let me know if you need more info/test, thanks. > > > > > > [...] > > > > > > > [ 4381.278858] ------------[ cut here ]------------ > > > > [ 4381.283484] WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 > > > > iomap_iter+0x32b/0x350 > > > > > > I can not recreate the WARN and the failure on my test machines. On the > > > other > > > hand, it is repeatedly recreated on CKI test machines since Feb/19/2024 > > > [1]. > > > > > > [1] https://datawarehouse.cki-project.org/issue/2508 > > > > > > I assume that a kernel change triggered the failure. > > > > > > Yi, is it possible to bisect and identify the trigger commit using CKI > > > test > > > machines? The failure is observed with v6.6.17 and v6.6.18 kernel. I > > > guess the > > > failure was not observed with v6.6.16 kernel, so I suggest to bisect > > > between > > Bisect shows it was introduced with the below commit: > > commit dbf8e63f48af48f3f0a069fc971c9826312dbfc1 > Author: Eunhee Rho <eunhee83....@samsung.com> > Date: Mon Aug 1 13:40:02 2022 +0900 > > f2fs: remove device type check for direct IO
Yi, thanks for bisecting. I hope Eunhee has time to check. > > I also attached the config file in case you want to reproduce it. The attached config file has this line: # CONFIG_F2FS_FS is not set But the WARN happened after f2fs mount, so this config should not be able to recreate the WARN. If you have time to afford, please check and share the config file again. _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
