On 04/06/2025 08.39, Christoph Hellwig wrote: > On Thu, Nov 28, 2024 at 04:52:30PM +0530, Anuj Gupta wrote: >> This adds a new io_uring interface to exchange additional integrity/pi >> metadata with read/write. >> >> Example program for using the interface is appended below [1]. >> >> The patchset is on top of block/for-next. >> >> Testing has been done by modifying fio: >> https://github.com/SamsungDS/fio/tree/priv/feat/pi-test-v11 > > It looks like this never got into upstream fio. Do you plan to submit > it? It would also be extremely useful to have a testing using it in > blktests, because it seems like we don't have any test coverage for the > read/write with metadata code at the moment. > > Just bringing this up because I want to be able to properly test the > metadata side of the nvme/block support for the new DMA mapping API > and I'm ѕtruggling to come up with good test coverage. > FWIW, we’re interested [1] in helping get this part properly tested as well. We're already running blktests in CI as part of kdevops, regularly testing against both linux-next and Linus' latest tags [2]. [1] https://lore.kernel.org/all/Z9v-1xjl7dD7Tr-H@xxxxxxxxxxxxxxxxxxxxxx/ [2] https://github.com/linux-kdevops/kdevops-ci/actions Shin'ichiro, the current CI implementation is still experimental (we are missing a few things like archive results and dashboard reporting) but we hope we can discuss soon the possibility to automatically reporting tests results to the mailing list
