From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org,
"Roger Pau Monné" <roger.pau@citrix.com>,
"committers@xenproject.org" <committers@xenproject.org>
Subject: Re: Regressed XSA-286, was [xen-unstable test] 161917: regressions - FAIL
Date: Wed, 16 Jun 2021 10:48:20 +0200 [thread overview]
Message-ID: <b57c2120-2f86-caa7-56ec-e215a7ad0529@suse.com> (raw)
In-Reply-To: <7cfa28ae-2fbe-0945-8a6c-a965ec52155f@citrix.com>
On 13.05.2021 22:15, Andrew Cooper wrote:
> On 13/05/2021 04:56, osstest service owner wrote:
>> flight 161917 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/161917/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>> test-arm64-arm64-examine 8 reboot fail REGR. vs. 161898
>> test-arm64-arm64-xl-thunderx 8 xen-boot fail REGR. vs. 161898
>> test-arm64-arm64-xl-credit1 8 xen-boot fail REGR. vs. 161898
>> test-arm64-arm64-xl-credit2 8 xen-boot fail REGR. vs. 161898
>> test-arm64-arm64-xl 8 xen-boot fail REGR. vs. 161898
>
> I reported these on IRC, and Julien/Stefano have already committed a fix.
>
>> Tests which are failing intermittently (not blocking):
>> test-xtf-amd64-amd64-3 92 xtf/test-pv32pae-xsa-286 fail in 161909 pass in 161917
>
> While noticing the ARM issue above, I also spotted this one by chance.
> There are two issues.
>
> First, I have reverted bed7e6cad30 and edcfce55917. The XTF test is
> correct, and they really do reintroduce XSA-286. It is a miracle of
> timing that we don't need an XSA/CVE against Xen 4.15.
As expressed at the time already, I view this reverting you did, without
there being any emergency and without you having gathered any acks or
allowed for objections, as overstepping your competencies. I did post a
patch to the XTF test, which I believe is wrong, without having had any
feedback there either. Unless I hear back by the end of this week with
substantial arguments of why I am wrong (which would need to also cover
the fact that an issue was found with 32-bit PAE only, in turn supporting
my view on the overall state), I intend to revert your revert early next
week.
Jan
next prev parent reply other threads:[~2021-06-16 8:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 3:56 [xen-unstable test] 161917: regressions - FAIL osstest service owner
2021-05-13 20:15 ` Regressed XSA-286, was " Andrew Cooper
2021-05-17 8:43 ` Jan Beulich
2021-05-17 10:59 ` Jan Beulich
2021-06-16 8:48 ` Jan Beulich [this message]
2021-06-16 15:43 ` Andrew Cooper
2021-06-17 11:56 ` Jan Beulich
2021-06-17 13:05 ` Ian Jackson
2021-06-17 14:40 ` Jan Beulich
2021-06-17 14:49 ` Ian Jackson
2021-06-17 14:55 ` Jan Beulich
2021-06-28 12:35 ` Ping: " Jan Beulich
2021-06-17 21:26 ` Stefano Stabellini
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=b57c2120-2f86-caa7-56ec-e215a7ad0529@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=committers@xenproject.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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).