ZTS: Add AlmaLinux 10

[mcmilk]

Motivation and Context

Description

How Has This Been Tested?

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Performance enhancement (non-breaking change which improves efficiency)
• Code cleanup (non-breaking change which makes code smaller or more readable)
• Quality assurance (non-breaking change which makes the code more robust against bugs)
• Breaking change (fix or feature that would cause existing functionality to change)
• Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
• Documentation (a change to man pages or other documentation)

Checklist:

• My code follows the OpenZFS code style requirements.
• I have updated the documentation accordingly.
• I have read the contributing document.
• I have added tests to cover my changes.
• I have run the ZFS Test Suite with this change applied.
• All commit messages are properly formatted and contain Signed-off-by.

[tonyhutter]

This should stop the almalinux10 test failures (patch untested):

diff --git a/tests/zfs-tests/tests/functional/direct/dio_async_fio_ioengines.ksh b/tests/zfs-tests/tests/functional/direct/dio_async_fio_ioengines.ksh
index 707dfeebd..670fedf3d 100755
--- a/tests/zfs-tests/tests/functional/direct/dio_async_fio_ioengines.ksh
+++ b/tests/zfs-tests/tests/functional/direct/dio_async_fio_ioengines.ksh
@@ -67,7 +67,8 @@ if is_linux; then
        if $(grep -q "CONFIG_IO_URING=y" /boot/config-$(uname -r)); then
                if [ -e /etc/os-release ] ; then
                        source /etc/os-release
-                       if [ $PLATFORM_ID = "platform:el9" ] ; then
+                       if [ $PLATFORM_ID = "platform:el9" ] || \
+                          [ $PLATFORM_ID = "platform:el10" ] ; then
                                log_note "io_uring disabled on RHEL 9 " \
                                "variants: fails with " \
                                "'Operation not permitted'"
diff --git a/tests/zfs-tests/tests/functional/io/io_uring.ksh b/tests/zfs-tests/tests/functional/io/io_uring.ksh
index 0b55eda01..e411dba94 100755
--- a/tests/zfs-tests/tests/functional/io/io_uring.ksh
+++ b/tests/zfs-tests/tests/functional/io/io_uring.ksh
@@ -47,7 +47,7 @@ fi
 
 if [ -e /etc/os-release ] ; then
        source /etc/os-release
-       if [ $PLATFORM_ID = "platform:el9" ]; then
+       if [ $PLATFORM_ID = "platform:el9" ] || [ $PLATFORM_ID = "platform:el10" ] ; then
                log_unsupported "Disabled on RHEL 9 variants: fails with 'Operation not permitted'"
        fi
 fi

[mcmilk]

This should stop the almalinux10 test failures (patch untested):
...

I hoped that io_uring got supported by RHEL :-/

[tonyhutter]

I hoped that io_uring got supported by RHEL :-/

Yea, I'm confused as well. The Alma 10 ZTS failures show:

07:32:50.51 NOTE: Checking Direct I/O with FIO async ioengine  io_uring with args --iodepth=4 --rw=rw
07:32:50.70 fio: pid=546710, err=1/file:engines/io_uring.c:1049, func=io_queue_init, error=Operation not permitted

But then again, I see this on Alma 9.6:

$  grep -i uring /boot/config-$(uname -r)
CONFIG_IO_URING=y

So I dunno 🤷‍♂️

[mcmilk]

I hoped that io_uring got supported by RHEL :-/

Yea, I'm confused as well. The Alma 10 ZTS failures show:

07:32:50.51 NOTE: Checking Direct I/O with FIO async ioengine  io_uring with args --iodepth=4 --rw=rw
07:32:50.70 fio: pid=546710, err=1/file:engines/io_uring.c:1049, func=io_queue_init, error=Operation not permitted

But then again, I see this on Alma 9.6:

$  grep -i uring /boot/config-$(uname -r)
CONFIG_IO_URING=y

So I dunno 🤷‍♂️

I found a way to enable io_uring on el9 + el10 ... I will provide a second commit tomorrow.

[mcmilk]

@behlendorf - should I rebase?

[amotin]

@mcmilk Yes, please.

[behlendorf]

Thanks for the rebase, I can merge this once the CI completes.