[Xen-devel] Which trees are supported (Was: Re: [qemu-upstream-4.2-testing test] 77180: regressions - FAIL)

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

So this arose because Stefano was unaware that 4.2 was no longer supported.
Neither am I ever confident about where the cut-off lie, e.g. I always have
to ask if I am doing backports for a security issue.

We should add rows toÂhttp://wiki.xen.org/wiki/Xen_Release_FeaturesÂright
under Initial Release giving first the date until which that tree is
supported with backports and second the date until which security support
will exist. We might also want to add a third "status" row. e.g.
"Supported", "Security Support only", "EOL" (we'll deal with extended
support by a third party when that next arises).

I'm happy to make the edits, however I don't know what dates I would write 
here. Taking it to be 18 months of Support and a further 18 months of
security support I would get:

                       Xen 4.0        Xen 4.1        Xen 4.2        Xen 4.3Â
        Xen 4.4Â        Xen 4.5Â        Xen 4.6
Initial Release        7 April 2010   25 March 2011  17 Sept 2012   9 July 
2013Â    10 March 2014Â  15 Jan 2015Â    13 Oct 2015Â
Supported until         EOL - ???       EOL - ???       EOL - ???       EOL - 
Jan 2015  EOL - Sept 2015 July 2016       April 2017
Security support til    EOL - ???       EOL - ???       EOL - ???       July 
2016       March 2016      Jan 2017        Oct 2018

(maybe those EOLs - ??? could be whatever the respective dates were, I
didn't try and backtrack to try and find out if reality matched the plan)

Ian.

On Thu, 2016-01-07 at 09:56 +0000, Ian Campbell wrote:
> On Wed, 2016-01-06 at 18:28 +0000, osstest service owner wrote:
> > flight 77180 qemu-upstream-4.2-testing real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/77180/
> > 
> > Regressions :-(
> > 
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> > Âbuild-i386ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ5 xen-buildÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂfail REGR.
> > vs. 62044
> > Âbuild-amd64ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ5 xen-buildÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂfail REGR.
> > vs. 62044
> 
> This is "man/xl.pod.1 around line 854: Expected text after =item, not a
> bullet" exposed by the Jessie upgrade.
> 
> However per Ian in <22154.35021.750846.695785@xxxxxxxxxxxxxxxxxxxxxxxx>Â[
> 0]
> :
> 
> ÂÂÂÂ...] 4.2 has had no commits since October - in particular, none
> ÂÂÂÂof the recent security fixes - and I would be reluctant to give it a
> ÂÂÂÂveneer of activity.
> 
> So our choices WRT these fixes in qemu-xen.git#staging-4.2, given they
> have
> already been pushed, are:
> 
> ÂÂÂ1. Fix xen.git#staging-4.2 to build on Jessie and wait for it to
> propagate.
> ÂÂÂ2. Revert the fixes from qemu-xen.git#staging-4.2 and force push the
> ÂÂÂÂÂÂresulting tree (which would be identical to something which
> previously
> ÂÂÂÂÂÂpassed).
> ÂÂÂ3. RollbackÂqemu-xen.git#staging-4.2.
> ÂÂÂ4. Force push.
> ÂÂÂ5. Drop a stop file.
> ÂÂÂ6. Shave yakks in osstest to allow per-branch selection of the Debian
> suite
> ÂÂÂÂÂÂand pin xen-4.2 and earlier to Wheezy.
> 
> #1 is contrary to the quote above, which makes a reasonable argument
> IMHO.
> 
> #3, #4 and #5 all seem like bad ideas to me.
> 
> #2 is a bit odd (to have the fixes in the branch but reverted), but seems
> least bad compared with #3..#5.
> 
> #6 is potentially a lot of work, but might be the right long term answer.
> 
> Ian.
> 
> [0]Âhttp://lists.xenproject.org/archives/html/xen-devel/2016-01/msg00112.
> html
> > 
> > Tests which did not succeed, but are not blocking:
> > Âbuild-i386-libvirtÂÂÂÂÂÂÂÂÂÂÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblockedÂÂn/a
> > Âtest-amd64-i386-xl-qemuu-win7-amd64ÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked n/a
> > Âtest-amd64-i386-qemuu-rhel6hvm-intelÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂÂÂÂÂblocked n/a
> > Âtest-i386-i386-xl-qemuu-winxpsp3ÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblockedÂÂn/a
> > Âtest-amd64-i386-xl-qemuu-ovmf-amd64ÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked n/a
> > Âtest-amd64-i386-qemuu-rhel6hvm-amdÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked n/a
> > Âtest-amd64-i386-xl-qemuu-winxpsp3-vcpus1ÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂblocked n/a
> > Âtest-amd64-i386-xend-qemuu-winxpsp3ÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked n/a
> > Âtest-amd64-i386-xl-qemuu-debianhvm-amd64ÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂblocked n/a
> > Âbuild-amd64-libvirtÂÂÂÂÂÂÂÂÂÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblockedÂÂn/a
> > Âtest-amd64-amd64-xl-qemuu-debianhvm-amd64ÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂblocked n/a
> > Âtest-amd64-amd64-xl-qemuu-win7-amd64ÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂÂÂÂÂblocked n/a
> > Âtest-amd64-amd64-xl-qemuu-winxpsp3ÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked n/a
> > Âtest-amd64-amd64-xl-qemuu-ovmf-amd64ÂÂ1 build-
> > check(1)ÂÂÂÂÂÂÂÂÂÂÂÂÂblocked n/a
> > 
> > version targeted for testing:
> > ÂqemuuÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ5081fc1c773d2a83ec7a867f030323b8b6956cd1
> > baseline version:
> > ÂqemuuÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂc17e602ae64fb24405ebd256679ba9a6f5819086
> > 
> > Last test of basisÂÂÂÂ62044ÂÂ2015-09-15 15:06:42 ZÂÂ113 days
> > Testing same sinceÂÂÂÂ66542ÂÂ2015-12-18 16:37:10 ZÂÂÂ19 daysÂÂÂ11
> > attempts
> > 
> > ------------------------------------------------------------
> > People who touched revisions under test:
> > Â Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> > 
> > jobs:
> > Âbuild-amd64ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂfailÂÂÂÂ
> > Âbuild-i386ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂfailÂÂÂÂ
> > Âbuild-amd64-libvirtÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âbuild-i386-libvirtÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âbuild-amd64-pvopsÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂpassÂÂÂÂ
> > Âbuild-i386-pvopsÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂpassÂÂÂÂ
> > Âtest-amd64-i386-qemuu-rhel6hvm-amdÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âtest-amd64-amd64-xl-qemuu-debianhvm-amd64ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âtest-amd64-i386-xl-qemuu-debianhvm-amd64ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âtest-amd64-amd64-xl-qemuu-ovmf-amd64ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âtest-amd64-i386-xl-qemuu-ovmf-amd64ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âtest-amd64-amd64-xl-qemuu-win7-amd64ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âtest-amd64-i386-xl-qemuu-win7-amd64ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âtest-amd64-i386-qemuu-rhel6hvm-intelÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âtest-amd64-i386-xl-qemuu-winxpsp3-vcpus1ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âtest-amd64-i386-xend-qemuu-winxpsp3ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âtest-amd64-amd64-xl-qemuu-winxpsp3ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > Âtest-i386-i386-xl-qemuu-winxpsp3ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂblocked 
> > 
> > 
> > ------------------------------------------------------------
> > sg-report-flight on osstest.test-lab.xenproject.org
> > logs: /home/logs/logs
> > images: /home/logs/images
> > 
> > Logs, config files, etc. are available at
> > ÂÂÂÂhttp://logs.test-lab.xenproject.org/osstest/logs
> > 
> > Explanation of these reports, and of osstest in general, is at
> > ÂÂÂÂhttp://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;
> > hb
> > =master
> > ÂÂÂÂhttp://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=mas
> > te
> > r
> > 
> > Test harness code can be found at
> > ÂÂÂÂhttp://xenbits.xen.org/gitweb?p=osstest.git;a=summary
> > 
> > 
> > Not pushing.
> > 
> > ------------------------------------------------------------
> > commit 5081fc1c773d2a83ec7a867f030323b8b6956cd1
> > Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> > Date:ÂÂÂFri Dec 18 15:45:14 2015 +0000
> > 
> > ÂÂÂÂxenfb: avoid reading twice the same fields from the shared page
> > ÂÂÂÂ
> > ÂÂÂÂReading twice the same field could give the guest an attack of
> > ÂÂÂÂopportunity. In the case of event->type, gcc could compile the
> > switch
> > ÂÂÂÂstatement into a jump table, effectively ending up reading the type
> > ÂÂÂÂfield multiple times.
> > ÂÂÂÂ
> > ÂÂÂÂThis is part of XSA-155.
> > ÂÂÂÂ
> > ÂÂÂÂSigned-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx
> > >
> > 
> > commit 74fab2ef4c0ba42af477e9e445c9883cc45cf9e6
> > Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> > Date:ÂÂÂFri Dec 18 15:44:58 2015 +0000
> > 
> > ÂÂÂÂxen/blkif: Avoid double access to src->nr_segments
> > ÂÂÂÂ
> > ÂÂÂÂsrc is stored in shared memory and src->nr_segments is dereferenced
> > ÂÂÂÂtwice at the end of the function.ÂÂIf a compiler decides to compile
> > this
> > ÂÂÂÂinto two separate memory accesses then the size limitation could be
> > ÂÂÂÂbypassed.
> > ÂÂÂÂ
> > ÂÂÂÂFix it by removing the double access to src->nr_segments.
> > ÂÂÂÂ
> > ÂÂÂÂThis is part of XSA-155.
> > ÂÂÂÂ
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel