❌ FAIL: Test report for kernel 5.11.0 (block)

❌ FAIL: Test report for kernel 5.11.0 (block)

[CKI Project]

Hello,

We ran automated tests on a recent commit from this kernel tree:

       Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
            Commit: 5c351b75f71a - Merge branch 'io_uring-worker.v3' into for-next

The results of these automated tests are provided below.

    Overall result: FAILED (see details below)
             Merge: OK
           Compile: OK
             Tests: FAILED

All kernel binaries, config files, and logs are available for download here:

  https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/02/23/624525

One or more kernel tests failed:

    s390x:
     ❌ Memory function: memfd_create
     ❌ AMTU (Abstract Machine Test Utility)

    ppc64le:
     ❌ storage: software RAID testing
     ❌ LTP
     ❌ Memory function: memfd_create
     ❌ AMTU (Abstract Machine Test Utility)

    aarch64:
     ❌ ACPI table test
     ❌ Memory function: memfd_create
     ❌ storage: SCSI VPD
     ❌ storage: software RAID testing

    x86_64:
     ❌ Storage SAN device stress - mpt3sas_gen1
     ❌ storage: software RAID testing
     ❌ Storage SAN device stress - lpfc driver
     ❌ Storage SAN device stress - qedf driver
     ❌ ACPI table test
     ❌ Memory function: memfd_create
     ❌ storage: SCSI VPD
     ❌ Storage SAN device stress - qla2xxx driver

We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.

Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.

        ,-.   ,-.
       ( C ) ( K )  Continuous
        `-',-.`-'   Kernel
          ( I )     Integration
           `-'
______________________________________________________________________________

Compile testing
---------------

We compiled the kernel for 4 architectures:

    aarch64:
      make options: make -j30 INSTALL_MOD_STRIP=1 targz-pkg

    ppc64le:
      make options: make -j30 INSTALL_MOD_STRIP=1 targz-pkg

    s390x:
      make options: make -j30 INSTALL_MOD_STRIP=1 targz-pkg

    x86_64:
      make options: make -j30 INSTALL_MOD_STRIP=1 targz-pkg



Hardware testing
----------------
We booted each kernel and ran the following tests:

  aarch64:
    Host 1:
       ✅ Boot test
       ❌ ACPI table test
       ✅ LTP
       ✅ Loopdev Sanity
       ✅ Memory: fork_mem
       ❌ Memory function: memfd_create
       ✅ AMTU (Abstract Machine Test Utility)
       ❌ storage: SCSI VPD
       🚧 ❌ CIFS Connectathon
       🚧 ❌ POSIX pjd-fstest suites
       🚧 ✅ Ethernet drivers sanity

    Host 2:
       ✅ Boot test
       ❌ storage: software RAID testing
       🚧 ❌ xfstests - ext4
       🚧 ✅ xfstests - xfs
       🚧 ✅ xfstests - btrfs
       🚧 ❌ Storage blktests
       🚧 ✅ Storage block - filesystem fio test
       🚧 ✅ Storage block - queue scheduler test
       🚧 ✅ Storage nvme - tcp
       🚧 ✅ Storage: swraid mdadm raid_module test
       🚧 ❌ stress: stress-ng

  ppc64le:
    Host 1:
       ✅ Boot test
       ❌ storage: software RAID testing
       🚧 ❌ xfstests - ext4
       🚧 ✅ xfstests - xfs
       🚧 ✅ xfstests - btrfs
       🚧 ❌ Storage blktests
       🚧 ✅ Storage block - filesystem fio test
       🚧 ✅ Storage block - queue scheduler test
       🚧 ✅ Storage nvme - tcp
       🚧 ✅ Storage: swraid mdadm raid_module test

    Host 2:
       ✅ Boot test
       ❌ LTP
       ✅ Loopdev Sanity
       ✅ Memory: fork_mem
       ❌ Memory function: memfd_create
       ❌ AMTU (Abstract Machine Test Utility)
       🚧 ❌ CIFS Connectathon
       🚧 ❌ POSIX pjd-fstest suites
       🚧 ✅ Ethernet drivers sanity

  s390x:
    Host 1:
       ✅ Boot test
       ✅ LTP
       ✅ Loopdev Sanity
       ✅ Memory: fork_mem
       ❌ Memory function: memfd_create
       ❌ AMTU (Abstract Machine Test Utility)
       🚧 ❌ CIFS Connectathon
       🚧 ❌ POSIX pjd-fstest suites
       🚧 ✅ Ethernet drivers sanity

    Host 2:
       ✅ Boot test
       🚧 ❌ Storage blktests
       🚧 ✅ Storage nvme - tcp
       🚧 ❌ Storage: swraid mdadm raid_module test
       🚧 ❌ stress: stress-ng

  x86_64:
    Host 1:
       ✅ Boot test
       ❌ Storage SAN device stress - mpt3sas_gen1

    Host 2:
       ✅ Boot test
       ❌ storage: software RAID testing
       🚧 ❌ xfstests - ext4
       🚧 ✅ xfstests - xfs
       🚧 ✅ xfstests - btrfs
       🚧 ✅ xfstests - nfsv4.2
       🚧 ✅ xfstests - cifsv3.11
       🚧 ❌ Storage blktests
       🚧 ✅ Storage block - filesystem fio test
       🚧 ✅ Storage block - queue scheduler test
       🚧 ✅ Storage nvme - tcp
       🚧 ✅ Storage: swraid mdadm raid_module test
       🚧 ❌ stress: stress-ng

    Host 3:
       ✅ Boot test
       ❌ Storage SAN device stress - lpfc driver

    Host 4:
       ✅ Boot test
       ❌ Storage SAN device stress - qedf driver

    Host 5:
       ✅ Boot test
       ❌ ACPI table test
       ✅ LTP
       ✅ Loopdev Sanity
       ✅ Memory: fork_mem
       ❌ Memory function: memfd_create
       ✅ AMTU (Abstract Machine Test Utility)
       ❌ storage: SCSI VPD
       🚧 ❌ CIFS Connectathon
       🚧 ❌ POSIX pjd-fstest suites
       🚧 ✅ Ethernet drivers sanity

    Host 6:
       ✅ Boot test
       ❌ Storage SAN device stress - qla2xxx driver

  Test sources: https://gitlab.com/cki-project/kernel-tests
    💚 Pull requests are welcome for new tests or improvements to existing tests!

Aborted tests
-------------
Tests that didn't complete running successfully are marked with ⚡⚡⚡.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.

Waived tests
------------
If the test run included waived tests, they are marked with 🚧. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.

Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with ⏱.

Re: ❌ FAIL: Test report for kernel 5.11.0 (block)

[Jens Axboe]

On 2/23/21 6:36 AM, Bruno Goncalves wrote:
> Hello,
> 
> In this run a lot of tests failed due to a known issue with SELinux policy, but 1 failure reported on LTP io_uring01 test when running on ppc64le might be a kernel bug [1].
> Note the sefgault (io_uring01[138555]: User access of kernel address (c0000000005a0258) - exploit attempt? (uid: 0)) on console log [2] when executing the test. The test logs are [3].
> 
> [1] https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/02/23/624525/build_ppc64le_redhat%3A1110530/tests/LTP/9600734_ppc64le_1_syscalls.fail.log
> [2] https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/02/23/624525/build_ppc64le_redhat%3A1110530/tests/9600734_ppc64le_1_console.log
> [3] https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/02/23/624525/build_ppc64le_redhat%3A1110530/tests/LTP/

That's my fault, for some reason I totally overlooked parisc and powerpc
in the PF_IO_WORKER change. Current for-next should work for you, this
is the change that fixes it:

https://git.kernel.dk/cgit/linux-block/commit/?h=io_uring-worker.v3&id=e4595c30ec3053a15d12615195b7a8726f9bee79

-- 
Jens Axboe

Re: ❌ FAIL: Test report for kernel 5.11.0 (block)

[Bruno Goncalves]

On Tue, Feb 23, 2021 at 7:59 PM Jens Axboe <axboe@kernel.dk> wrote:
>
> On 2/23/21 6:36 AM, Bruno Goncalves wrote:
> > Hello,
> >
> > In this run a lot of tests failed due to a known issue with SELinux policy, but 1 failure reported on LTP io_uring01 test when running on ppc64le might be a kernel bug [1].
> > Note the sefgault (io_uring01[138555]: User access of kernel address (c0000000005a0258) - exploit attempt? (uid: 0)) on console log [2] when executing the test. The test logs are [3].
> >
> > [1] https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/02/23/624525/build_ppc64le_redhat%3A1110530/tests/LTP/9600734_ppc64le_1_syscalls.fail.log
> > [2] https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/02/23/624525/build_ppc64le_redhat%3A1110530/tests/9600734_ppc64le_1_console.log
> > [3] https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/02/23/624525/build_ppc64le_redhat%3A1110530/tests/LTP/
>
> That's my fault, for some reason I totally overlooked parisc and powerpc
> in the PF_IO_WORKER change. Current for-next should work for you, this
> is the change that fixes it:
>
> https://git.kernel.dk/cgit/linux-block/commit/?h=io_uring-worker.v3&id=e4595c30ec3053a15d12615195b7a8726f9bee79

Thanks for the fix, the test now passes.

Bruno Goncalves

>
> --
> Jens Axboe
>