From: Will Deacon <will@kernel.org>
To: CKI Project <cki-project@redhat.com>, mark.rutland@arm.com
Cc: guoqing.jiang@cloud.ionos.com,
Rachel Sibley <rasibley@redhat.com>,
Xiong Zhou <xzhou@redhat.com>,
catalin.marinas@arm.com, Memory Management <mm-qe@redhat.com>,
skt-results-master@redhat.com, colyli@suse.de,
Song Liu <song@kernel.org>,
xni@redhat.com, Jan Stancek <jstancek@redhat.com>,
linux-arm-kernel@lists.infradead.org,
Changhui Zhong <czhong@redhat.com>
Subject: Re: ❌ FAIL: Test report for kernel 5.10.0-rc5 (arm-next)
Date: Fri, 27 Nov 2020 09:09:22 +0000 [thread overview]
Message-ID: <20201127090922.GA19927@willie-the-truck> (raw)
In-Reply-To: <cki.7D4B12771B.V80WLD4Z5J@redhat.com>
[+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
next prev parent reply other threads:[~2020-11-27 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 7:58 ❌ FAIL: Test report for kernel 5.10.0-rc5 (arm-next) CKI Project
2020-11-27 9:09 ` Will Deacon [this message]
2020-11-27 10:13 ` Xiao Ni
-- strict thread matches above, loose matches on Subject: below --
2020-11-26 17:57 CKI Project
2020-11-26 18:43 ` ? " Mark Rutland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201127090922.GA19927@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cki-project@redhat.com \
--cc=colyli@suse.de \
--cc=czhong@redhat.com \
--cc=guoqing.jiang@cloud.ionos.com \
--cc=jstancek@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mm-qe@redhat.com \
--cc=rasibley@redhat.com \
--cc=skt-results-master@redhat.com \
--cc=song@kernel.org \
--cc=xni@redhat.com \
--cc=xzhou@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).