❌ FAIL: Test report for kernel 5.10.0-rc5 (arm-next)

❌ FAIL: Test report for kernel 5.10.0-rc5 (arm-next)

[CKI Project]

[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]


Hello,

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

       Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
            Commit: 9be6c84caac4 - Merge branch 'entry-tracing' into for-kernelci

The results of these automated tests are provided below.

    Overall result: FAILED (see details below)
             Merge: OK
           Compile: 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/2020/11/26/618748

We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:

           aarch64: FAILED (see build-aarch64.log.xz attachment)

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 1 architecture:

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



[-- Attachment #2: build-aarch64.log.xz --]
[-- Type: application/x-xz, Size: 21372 bytes --]

[-- Attachment #3: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: ? FAIL: Test report for kernel 5.10.0-rc5 (arm-next)

[Mark Rutland]

On Thu, Nov 26, 2020 at 05:57:10PM -0000, CKI Project wrote:
> 
> Hello,
> 
> We ran automated tests on a recent commit from this kernel tree:
> 
>        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
>             Commit: 9be6c84caac4 - Merge branch 'entry-tracing' into for-kernelci
> 
> The results of these automated tests are provided below.
> 
>     Overall result: FAILED (see details below)
>              Merge: OK
>            Compile: 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/2020/11/26/618748
> 
> We attempted to compile the kernel for multiple architectures, but the compile
> failed on one or more architectures:
> 
>            aarch64: FAILED (see build-aarch64.log.xz attachment)

My bad; I messed up converting the SDEI code. I've sent a trivial fixup
in reply to the original broken patch.

Thanks,
Mark.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

❌ FAIL: Test report for kernel 5.10.0-rc5 (arm-next)

[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/arm64/linux.git
            Commit: 770428a3d2c3 - arm64: sdei: fix arm64_{enter,exit}_nmi() calls

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/2020/11/26/618759

One or more kernel tests failed:

    aarch64:
     ❌ LTP
     ❌ storage: software RAID testing

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 1 architecture:

    aarch64:
      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
       ✅ ACPI enabled test
       ❌ LTP
       ✅ Loopdev Sanity
       ✅ Memory: fork_mem
       ✅ Memory function: memfd_create
       ✅ AMTU (Abstract Machine Test Utility)
       ✅ Networking bridge: sanity
       ✅ Networking socket: fuzz
       ✅ 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
       ✅ Libkcapi AF_ALG test
       ✅ pciutils: update pci ids test
       ✅ ALSA PCM loopback test
       ✅ ALSA Control (mixer) Userspace Element test
       ✅ storage: SCSI VPD
       🚧 ✅ CIFS Connectathon
       🚧 ✅ POSIX pjd-fstest suites
       🚧 ✅ Firmware test suite
       🚧 ✅ jvm - jcstress tests
       🚧 ✅ Memory function: kaslr
       🚧 ✅ Ethernet drivers sanity
       🚧 ✅ Networking firewall: basic netfilter test
       🚧 ✅ audit: audit testsuite test
       🚧 ✅ trace: ftrace/tracer
       🚧 ✅ kdump - kexec_boot

    Host 2:
       ✅ Boot test
       ✅ selinux-policy: serge-testsuite
       ❌ storage: software RAID testing
       ✅ stress: stress-ng
       🚧 ❌ xfstests - ext4
       🚧 ✅ xfstests - xfs
       🚧 ✅ xfstests - btrfs
       🚧 ❌ IPMI driver test
       🚧 ✅ IPMItool loop stress test
       🚧 ✅ Storage blktests
       🚧 ✅ Storage block - filesystem fio test
       🚧 ✅ Storage block - queue scheduler test
       🚧 ✅ Storage nvme - tcp
       🚧 ✅ Storage: swraid mdadm raid_module test

  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 ⏱.


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: ❌ FAIL: Test report for kernel 5.10.0-rc5 (arm-next)

[Will Deacon]

[+Mark, since this is basically hammering on his lockdep/tracing fixes]

On Fri, Nov 27, 2020 at 07:58:13AM -0000, CKI Project wrote:
> We ran automated tests on a recent commit from this kernel tree:
> 
>        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
>             Commit: 770428a3d2c3 - arm64: sdei: fix arm64_{enter,exit}_nmi() calls
> 
> 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/2020/11/26/618759
> 
> One or more kernel tests failed:
> 
>     aarch64:
>      ❌ LTP

This guy is just perf_event_open02, and I'm not worried about it. The
overhead of PROVE_LOCKING and friends is likely the culprit (and I see
stuff in dmesg about throttling the sample period).

>      ❌ storage: software RAID testing

This one has an interested RCU splat, but it looks like a straight-up
bug to me:

  drivers/md/raid10.c:1732 suspicious rcu_dereference_check() usage!

as there appears to be two calls to rcu_dereference() outside of a read-side
critical section introduced relatively recently by bcc90d280465 ("md/raid10:
improve raid10 discard request"). 

I've added the folks from that commit. Full logs at:

https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2020/11/26/618759/build_aarch64_redhat%3A1038231/tests/storage_software_RAID_testing/9107170_aarch64_2_dmesg.log

But anyway, Mark, your stuff seems to be holding up. Thanks.

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: ❌ FAIL: Test report for kernel 5.10.0-rc5 (arm-next)

[Xiao Ni]

On 11/27/2020 05:09 PM, Will Deacon wrote:
> [+Mark, since this is basically hammering on his lockdep/tracing fixes]
>
> On Fri, Nov 27, 2020 at 07:58:13AM -0000, CKI Project wrote:
>> We ran automated tests on a recent commit from this kernel tree:
>>
>>         Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
>>              Commit: 770428a3d2c3 - arm64: sdei: fix arm64_{enter,exit}_nmi() calls
>>
>> 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/2020/11/26/618759
>>
>> One or more kernel tests failed:
>>
>>      aarch64:
>>       ❌ LTP
> This guy is just perf_event_open02, and I'm not worried about it. The
> overhead of PROVE_LOCKING and friends is likely the culprit (and I see
> stuff in dmesg about throttling the sample period).
>
>>       ❌ storage: software RAID testing
> This one has an interested RCU splat, but it looks like a straight-up
> bug to me:
>
>    drivers/md/raid10.c:1732 suspicious rcu_dereference_check() usage!
>
> as there appears to be two calls to rcu_dereference() outside of a read-side
> critical section introduced relatively recently by bcc90d280465 ("md/raid10:
> improve raid10 discard request").
>
> I've added the folks from that commit. Full logs at:
>
> https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2020/11/26/618759/build_aarch64_redhat%3A1038231/tests/storage_software_RAID_testing/9107170_aarch64_2_dmesg.log
>
> But anyway, Mark, your stuff seems to be holding up. Thanks.
>
> Will
>
Hi Will

Thanks for pointing about this.

rdev must have value at this time. Because it already adds the 
rdev->nr_pending before this for loop
when it needs to send flush bio to this rdev. So the patch should fix 
this problem.

Hi, Song, do you think the following patch is good?


diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
index 3153183..7324a7d 100644
--- a/drivers/md/raid10.c
+++ b/drivers/md/raid10.c
@@ -1729,9 +1729,8 @@ static int raid10_handle_discard(struct mddev 
*mddev, struct bio *bio)
         for (disk = 0; disk < geo->raid_disks; disk++) {
                 sector_t dev_start, dev_end;
                 struct bio *mbio, *rbio = NULL;
-               struct md_rdev *rdev = 
rcu_dereference(conf->mirrors[disk].rdev);
-               struct md_rdev *rrdev = rcu_dereference(
-                       conf->mirrors[disk].replacement);
+               struct md_rdev *rdev = conf->mirrors[disk].rdev;
+               struct md_rdev *rrdev = conf->mirrors[disk].replacement;

                 /*
                  * Now start to calculate the start and end address for 
each disk.

Regards
Xiao


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel