From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] ❌ FAIL: Test report for kernel 5.5.7-60528b7.cki (stable-queue)
Date: Thu, 5 Mar 2020 11:56:02 -0500 (EST) [thread overview]
Message-ID: <173385062.10432633.1583427362328.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <2065777364.10425170.1583425488638.JavaMail.zimbra@redhat.com>
----- Original Message -----
>
>
> ----- Original Message -----
> >
> > 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: 60528b79e30a - kvm: nVMX: VMWRITE checks unsupported
> > field before read-only field
> >
> > 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://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/03/04/471505
> >
> > One or more kernel tests failed:
> >
> > s390x:
> > ? LTP
>
> All instances of similar panics [1] manifest mostly on s390 and at
> first glance look like memory corruptions.
>
> I'm looking to confirm, whether this has been fixed by:
>
> commit 6fcca0fa48118e6d63733eb4644c6cd880c15b8f
> Author: Suren Baghdasaryan <surenb@google.com>
> Date: Mon Feb 3 13:22:16 2020 -0800
>
> sched/psi: Fix OOB write when writing 0 bytes to PSI files
It's unrelated. The test does read, not write.
5.6.0-0.rc3 crashed as well. On s390x I'm using it's enough to
"cat /sys/fs/cgroup/cpu.pressure" to trigger.
next prev parent reply other threads:[~2020-03-05 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 6:24 [LTP] ❌ FAIL: Test report for kernel 5.5.7-60528b7.cki (stable-queue) CKI Project
2020-03-05 16:24 ` Jan Stancek
2020-03-05 16:56 ` Jan Stancek [this message]
2020-03-08 20:07 ` Jan Stancek
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=173385062.10432633.1583427362328.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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