zfs 2.1.11 compilation failures on 6.3.4-201.fc38.x86_64

[thwalker3]

My apologies in advance if this has already been reported. I searched around and found a few non-github mentions of this, but not an open issue.

Yes, I know that the dkms package states that it is only tested and verified working through 6.2 but, since this kernel hit Fedora 38 in the last day or so, others will likely begin to run in to it.
Long story short, configure fails with:

checking whether revalidate_disk() is available... no
checking whether get_disk_ro() is available... yes
checking whether generic_readlink is global... no
checking whether ql->discard_granularity is available... yes
checking whether inode_owner_or_capable() exists... no
checking whether inode_owner_or_capable() takes user_ns... configure: error: 
        *** None of the expected "capability" interfaces were detected.
        *** This may be because your kernel version is newer than what is
        *** supported, or you are using a patched custom kernel with
        *** incompatible modifications.
        ***
        *** ZFS Version: zfs-2.1.11-1
        *** Compatible Kernels: 3.10 - 6.2

This appears to be due to this upstream commit. I haven't had a chance to dig much further yet.

[behlendorf]

Thanks for letting us know. There are several other 6.3 kernel compatibility changes which will need to be backported for 2.1.12. For the moment you'll need to stick with the 6.2 kernel.

[sunilvaltix]

@behlendorf 6.2 got EOL'ed upstream at 6.2.16. And there have been 2 patch releases on top of 6.3.x since, which are not going to be in 6.2.17. So, sticking with 6.2 is not a realistic option. Downgrading to 6.1.x is an option but who wants to go back. Where is the fun in that....:-)

[arda2012]

First of all, I have much respect for people spending much of their free time developing open source software. However as linux kernel 6.3 is now out for over a month and kernel 6.2.16 is EOL, it would be nice to hear about the future plannings.

Will 2.1.12 be released soon (1-2 weeks) ?
Or will it be more like months ?
Will 2.1.12 support kernel 6.3 or will this support be added later ?
How about master ? Are people using it ? I know that master is work in progress, but is it stable enough for normal use ?

I know when developing in free time, it is not simple to do any estimations when something will be ready, but it would help people having a rough approximation.

Thanks in advance

[thwalker3]

It does appear as though there has been a bunch of related activity on zfs-2.1.12-staging today, which is encouraging. I'm still a little confused why the configure check still fails for me after:

commit f0aca5f7bb0965f3a7a1e501b6ec1873bdcb2c73
Author: youzhongyang <youzhong@gmail.com>
Date:   Mon Apr 10 17:15:36 2023 -0400

    Linux 6.3 compat: idmapped mount API changes

    Linux kernel 6.3 changed a bunch of APIs to use the dedicated idmap
    type for mounts (struct mnt_idmap), we need to detect these changes
    and make zfs work with the new APIs.

    NOTE: This backport only includes the configure checks to detect
    the 6.3 idmap API changes.  It does not include support for idmap.
    When provided the idmap variable is ignored in most case in the
    same way the user_ns argument was ignored.  This change is solely
    to provide compatibility with the new interfaces.

    Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
    Signed-off-by: Youzhong Yang <yyang@mathworks.com>
    Closes #14682

Reading #14682 though, I can now appreciate how big the changes are for even this one upstream patch (and there are multiple others that broke things in 6.3).

So I will patiently await 2.1.12. Thank you @behlendorf, @tonyhutter, @youzhongyang, and all the other devs for all of the hard work!

[behlendorf]

We expect 2.1.12 to be tagged in the next 1-2 weeks with support for the 6.3 kernel (#14942). Updating the code to be compatible with the 6.3 kernel was a bigger than usual lift as the needed changes were fairly extensive.

[AkechiShiro]

@behlendorf do you happen to know if for 6.4 the hurdle will be big as well or haven't taken a look yet or it will be more smooth ?

[behlendorf]

I haven't taken a close look yet, but at the moment we're only carrying one small patch for the 6.4 kernel. This was added to the 2.1.12 patch stack so it's possible it will work, we'll have to see what the final release looks like.

[stale]

This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.