❌ PANICKED: Test report for kernel 5.5.8-6afe1f4.cki (stable-queue)

Hello,

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

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Commit: 6afe1f4aeae9 - ASoC: topology: Fix memleak in soc_tplg_manifest_load()

The results of these automated tests are provided below.

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

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

https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/03/09/480618

One or more kernel tests failed:

    s390x:
     ? LTP

    ppc64le:
     ? LTP
     ? audit: audit testsuite test

    aarch64:
     ? audit: audit testsuite test

    x86_64:
     ? audit: audit testsuite test

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: -j30 INSTALL_MOD_STRIP=1 targz-pkg

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

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

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

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

aarch64:
Host 1:
? Boot test
? Podman system integration test - as root ? Podman system integration test - as user ? LTP
? Loopdev Sanity
? Memory function: memfd_create
? AMTU (Abstract Machine Test Utility) ? Networking bridge: sanity
? Ethernet drivers sanity
? Networking MACsec: sanity
? Networking socket: fuzz
? Networking sctp-auth: sockopts test ? Networking: igmp conformance test
? Networking route: pmtu
? Networking route_func - local
? Networking route_func - forward
? Networking TCP: keepalive test
? Networking UDP: socket
? Networking tunnel: geneve basic test ? Networking tunnel: gre basic
? L2TP basic test
? Networking tunnel: vxlan basic
? Networking ipsec: basic netns - transport ? Networking ipsec: basic netns - tunnel ? audit: audit testsuite test
? httpd: mod_ssl smoke sanity
? tuned: tune-processes-through-perf ? ALSA PCM loopback test
? ALSA Control (mixer) Userspace Element test ? storage: SCSI VPD
? trace: ftrace/tracer
? ? CIFS Connectathon
? ? POSIX pjd-fstest suites
? ? jvm - DaCapo Benchmark Suite
? ? jvm - jcstress tests
? ? Memory function: kaslr
? ? LTP: openposix test suite
? ? Networking vnic: ipvlan/basic
? ? iotop: sanity
? ? Usex - version 1.9-29
? ? storage: dm/common

Host 2:
? Boot test
? xfstests - ext4
? xfstests - xfs
? selinux-policy: serge-testsuite
? lvm thinp sanity
? storage: software RAID testing
? stress: stress-ng
? ? IPMI driver test
? ? IPMItool loop stress test
? ? Storage blktests

ppc64le:
Host 1:

? Internal infrastructure issues prevented one or more tests (marked with ???) from running on this architecture.
This is not the fault of the kernel that was tested.

? Boot test
??? Podman system integration test - as root ??? Podman system integration test - as user ??? LTP
??? Loopdev Sanity
??? Memory function: memfd_create
??? AMTU (Abstract Machine Test Utility) ??? Networking bridge: sanity
??? Ethernet drivers sanity
??? Networking MACsec: sanity
??? Networking socket: fuzz
??? Networking sctp-auth: sockopts test ??? Networking route: pmtu
??? Networking route_func - local
??? Networking route_func - forward ??? Networking TCP: keepalive test
??? Networking UDP: socket
??? Networking tunnel: geneve basic test ??? Networking tunnel: gre basic
??? L2TP basic test
??? Networking tunnel: vxlan basic
??? Networking ipsec: basic netns - tunnel ??? audit: audit testsuite test
??? httpd: mod_ssl smoke sanity
??? tuned: tune-processes-through-perf ??? ALSA PCM loopback test
??? ALSA Control (mixer) Userspace Element test ??? trace: ftrace/tracer
? ??? CIFS Connectathon
? ??? POSIX pjd-fstest suites
? ??? jvm - DaCapo Benchmark Suite
? ??? jvm - jcstress tests
? ??? Memory function: kaslr
? ??? LTP: openposix test suite
? ??? Networking vnic: ipvlan/basic
? ??? iotop: sanity
? ??? Usex - version 1.9-29
? ??? storage: dm/common

Host 2:
? Boot test
? xfstests - ext4
? xfstests - xfs
? selinux-policy: serge-testsuite
? lvm thinp sanity
? storage: software RAID testing
? ? IPMI driver test
? ? IPMItool loop stress test
? ? Storage blktests

Host 3:
? Boot test
? Podman system integration test - as root ? Podman system integration test - as user ? LTP
? Loopdev Sanity
? Memory function: memfd_create
? AMTU (Abstract Machine Test Utility) ? Networking bridge: sanity
? Ethernet drivers sanity
? Networking MACsec: sanity
? Networking socket: fuzz
? Networking sctp-auth: sockopts test ? Networking route: pmtu
? Networking route_func - local
? Networking route_func - forward
? Networking TCP: keepalive test
? Networking UDP: socket
? Networking tunnel: geneve basic test ? Networking tunnel: gre basic
? L2TP basic test
? Networking tunnel: vxlan basic
? Networking ipsec: basic netns - tunnel ? audit: audit testsuite test
? httpd: mod_ssl smoke sanity
? tuned: tune-processes-through-perf ? ALSA PCM loopback test
? ALSA Control (mixer) Userspace Element test ? trace: ftrace/tracer
? ? CIFS Connectathon
? ? POSIX pjd-fstest suites
? ? jvm - DaCapo Benchmark Suite
? ? jvm - jcstress tests
? ? Memory function: kaslr
? ? LTP: openposix test suite
? ? Networking vnic: ipvlan/basic
? ? iotop: sanity
? ? Usex - version 1.9-29
? ? storage: dm/common

s390x:
Host 1:
? Boot test
? selinux-policy: serge-testsuite
? stress: stress-ng
? ? Storage blktests

Host 2:
? Boot test
? Podman system integration test - as root ? Podman system integration test - as user ? LTP
??? Loopdev Sanity
??? Memory function: memfd_create
??? Networking bridge: sanity
??? Ethernet drivers sanity
??? Networking MACsec: sanity
??? Networking sctp-auth: sockopts test ??? Networking route: pmtu
??? Networking route_func - local
??? Networking route_func - forward ??? Networking TCP: keepalive test ??? Networking UDP: socket
??? Networking tunnel: geneve basic test ??? Networking tunnel: gre basic
??? L2TP basic test
??? Networking tunnel: vxlan basic ??? Networking ipsec: basic netns - transport ??? Networking ipsec: basic netns - tunnel ??? audit: audit testsuite test
??? httpd: mod_ssl smoke sanity
??? tuned: tune-processes-through-perf ??? trace: ftrace/tracer
? ??? CIFS Connectathon
? ??? POSIX pjd-fstest suites
? ??? jvm - DaCapo Benchmark Suite
? ??? jvm - jcstress tests
? ??? Memory function: kaslr
? ??? LTP: openposix test suite
? ??? Networking vnic: ipvlan/basic
? ??? iotop: sanity
? ??? Usex - version 1.9-29
? ??? storage: dm/common

x86_64:
Host 1:
? Boot test
? Storage SAN device stress - mpt3sas driver

Host 2:
? Boot test
? Storage SAN device stress - megaraid_sas

Host 3:

? Internal infrastructure issues prevented one or more tests (marked with ???) from running on this architecture.
This is not the fault of the kernel that was tested.

??? Boot test
??? xfstests - ext4
??? xfstests - xfs
??? selinux-policy: serge-testsuite ??? lvm thinp sanity
??? storage: software RAID testing ??? stress: stress-ng
? ??? IOMMU boot test
? ??? IPMI driver test
? ??? IPMItool loop stress test
? ??? power-management: cpupower/sanity test ? ??? Storage blktests

Host 4:
? Boot test
? Podman system integration test - as root ? Podman system integration test - as user ? LTP
? Loopdev Sanity
? Memory function: memfd_create
? AMTU (Abstract Machine Test Utility) ? Networking bridge: sanity
? Ethernet drivers sanity
? Networking MACsec: sanity
? Networking socket: fuzz
? Networking sctp-auth: sockopts test ? Networking: igmp conformance test
? Networking route: pmtu
? Networking route_func - local
? Networking route_func - forward
? Networking TCP: keepalive test
? Networking UDP: socket
? Networking tunnel: geneve basic test ? Networking tunnel: gre basic
? L2TP basic test
? Networking tunnel: vxlan basic
? Networking ipsec: basic netns - transport ? Networking ipsec: basic netns - tunnel ? audit: audit testsuite test
? httpd: mod_ssl smoke sanity
? tuned: tune-processes-through-perf ? pciutils: sanity smoke test
? ALSA PCM loopback test
? ALSA Control (mixer) Userspace Element test ? storage: SCSI VPD
? trace: ftrace/tracer
? ? CIFS Connectathon
? ? POSIX pjd-fstest suites
? ? jvm - DaCapo Benchmark Suite
? ? jvm - jcstress tests
? ? Memory function: kaslr
? ? LTP: openposix test suite
? ? Networking vnic: ipvlan/basic
? ? iotop: sanity
? ? Usex - version 1.9-29
? ? storage: dm/common

Host 5:
? Boot test
? xfstests - ext4
? xfstests - xfs
? selinux-policy: serge-testsuite
? lvm thinp sanity
? storage: software RAID testing
? stress: stress-ng
? ? IOMMU boot test
? ? Storage blktests

Test sources: https://github.com/CKI-project/tests-beaker
? 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 ?.

Given that there's nothing I can do about this, I'm just starting to flat-out ignore the results of these emails :(

greg k-h

Hi Greg, I'm sorry for all the noise, the fix has already been posted here:
https://lore.kernel.org/lkml/[email protected]/

While we wait for it to make into stable-queue, I'm working on masking this panic in CKI. There were several tests which could trigger the panic, not just LTP, so we need to mask it in a way that we don't mask real problems.

In the mean time I have already waived the audit failures, you should no longer see these failures for new pipelines triggered.

audit-testsuite started failing recently (yesterday) because a lot of work was merged upstream and some new tests are testing functionality not available in RHEL yet. Please waive all audit-testsuite results and I will correct our beaker wrapper in the meantime.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20200310/2ed21a16/attachment-0001.htm>