From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [xen-4.9-testing test] 132484: regressions - FAIL
Date: Wed, 30 Jan 2019 12:50:23 +0000 [thread overview]
Message-ID: <87b13ff2-7068-d2be-f60c-4894451e61dd@citrix.com> (raw)
In-Reply-To: <5C519BE802000078002124FD@prv1-mh.provo.novell.com>
On 30/01/2019 12:43, Jan Beulich wrote:
>>>> On 29.01.19 at 19:55, <andrew.cooper3@citrix.com> wrote:
>> On 29/01/2019 18:49, osstest service owner wrote:
>>> flight 132484 xen-4.9-testing real [real]
>>> http://logs.test-lab.xenproject.org/osstest/logs/132484/
>>>
>>> Regressions :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> including tests which could not be run:
>>> test-xtf-amd64-amd64-1 69 xtf/test-hvm64-xsa-278 fail REGR. vs. 130954
>> This is the XSA-278 PoC noticing that c/s
>> 75ce36eb72cb93e8a3c9f60fd5e697067921d712 hasn't been backported.
> I've just added this to the pending set, but I have to admit that
> it wasn't clear to me at all that this would be needed on the stable
> trees. There was a remark about backportability in the submission,
> but this didn't mean to me that it's kind of imperative to have.
This particular bug (and bugfix) was found completely unexpectedly by
the XSA-278 PoC.
There is no critical need to backport the bugfix (as it is indeed
benign), except for the fact that because OSSTest has observed that the
PoC fails on that specific hardware, it has come to the (incorrect)
conclusion that we've recently regressed the 4.9 branch.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-01-30 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 18:49 [xen-4.9-testing test] 132484: regressions - FAIL osstest service owner
2019-01-29 18:55 ` Andrew Cooper
2019-01-30 12:43 ` Jan Beulich
2019-01-30 12:50 ` Andrew Cooper [this message]
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=87b13ff2-7068-d2be-f60c-4894451e61dd@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.