Brian Behlendorf

@darrenfreeman testing on Ubuntu 18.04, with the final 0.8.0 release, I wasn't able to reproduce the issue using your reproducer. Would it be possible for you to update to zfs-0.8.0...

These warnings can be safely ignored and will not result in a build failure unless compiling a debug build with `--enable-debug`. It's largely a matter of both the 5.18 kernel...

What is being staged for 2.1.6 can found in the staging branch, https://github.com/openzfs/zfs/tree/zfs-2.1.6-staging. It'd be great if you could give it a try and verify it does in fact resolve...

True, but in the master branch the `icp` kmod has now been merged in the `zfs` kmod on Linux.

The `cache/cache_012_pos` failure looks like it was somehow introduced by this change. The other failures we've seen before.

Looks good. Unfortunately, it looks like a couple small bugs have been introduced in other changes which `ztest` is now hitting quite often. That needs to be investigated, but you're...

Unfortunately, it looks like this breaks the build on CentOS 7 and the old ppc64 builder due to the old `gcc` version. Seems like a configure check will be needed...

It looks like you managed to hit a bug in `abidiff` ``` abidiff: ../../src/abg-reader.cc:4616: abigail::ir::union_decl_sptr abigail::xml_reader::build_union_decl(abigail::xml_reader::read_context&, xmlNodePtr, bool): Assertion `previous_definition->get_name() == name' failed. ``` You might try using the version...

This one would be nice to get wrapped up. I've added myself as a reviewer and have tagged a few people for reviews.

@abrasive thank you for identifying the root cause here. If possible would you mind verifying the proposed fix in #7393.