blktests failures with v6.15 kernel

Daniel Wagner dwagner at suse.de
Fri Jun 6 07:58:31 PDT 2025


On Fri, Jun 06, 2025 at 10:25:25PM +0800, Yi Zhang wrote:
> > As of today, CKI project keeps on reporting the failure:
> >
> >   https://datawarehouse.cki-project.org/kcidb/tests/redhat:1851238698-aarch64-kernel_upt_7
> >
> > Yi, do you think the new libnvme release will help to silence the failure
> 
> I've created one CKI issue to track the nvme/023 failure, so the
> failure will be waived in the future test.
> 
> > reports? I'm guessing the release will help RedHat to pick up and apply to CKI
> 
> Yes, if we have the new release for libnvme, our Fedora libnvme
> maintainer can build the new one for Fedora. I also created the Fedora
> issue to track it on libnvme side.

Sure; a stop gap solution, just don't build with liburing. In hindsight,
I should have set it to disabled per default, will do it now.

FWIW, the contributor for the io_uring feature, stated that it improved
the performance for some workloads. Though, I think the whole
integration is sub-optimal, as a new io_uring is created/configured for
each get_log_page call. So only for a large transfers there is going to
help.

I am currently working on libnvme 2 and I think we can improve this
quite a bit though. But for libnvme 1 I'd  recommend to disable
liburing.



More information about the Linux-nvme mailing list