Upstream issue: https://github.com/openzfs/zfs/issues/15930 Fix: https://github.com/openzfs/zfs/pull/15931 Potential actions: 1) Add a warning in post-install/dkms scripts. 2) Ship the patch. Reproducible: Always
About 1) we might as well just backport this: https://github.com/openzfs/zfs/pull/15986
Seems the bug is in the kernel module, not userspace.
I believe zfs-kmod-2.2.3 already dies in pkg_setup for kernels >= 6.8.
Of course I'm sorry, it's in the dkms not in the utils. I'm using btrfs on Gentoo so I've tested the dkms for 2.2.3 only on Arch Linux. Unless Gentoo added a kernel check for supported versions it should compile because compat patches for 6.8 landed in 2.2.3.
(In reply to darkbasic from comment #4) > Of course I'm sorry, it's in the dkms not in the utils. > I'm using btrfs on Gentoo so I've tested the dkms for 2.2.3 only on Arch > Linux. Unless Gentoo added a kernel check for supported versions it should > compile because compat patches for 6.8 landed in 2.2.3. Gentoo has had such a check for ages. Per https://github.com/openzfs/zfs/releases/tag/zfs-2.2.3, 2.2.3 was officially marked as only supporting 6.7. We track the official supported ranges.
You keep referring to dkms. I have no idea how that works. Copying the dkms maintainer; perhaps he has some idea of what you are talking about.
dkms is not used here. It's a system for rebuilding external kernel modules and it's used for kernel modules that are *not* handled by portage. zfs-kmod is a linux-mod-r1 ebuild and does not install a dkms configuration file, nor does it register itself with the dkms database. You are correct though that on Arch, dkms is used for zfs-kmod.
