4.5.3 preparations

4.5.3 preparations

[Jan Beulich]

All,

it just occurred to me that 4.5.2 has been a while back, and indeed
4.5.3 would be due later this week. This may be a little too eager,
but I'd like to aim at getting this out at least some time next week.
Besides what is in the tree already, I have three more commits I
intend to backport:
0640ffb67f	x86emul: fix rIP handling
1329105943	x86/hvm: print register state upon triple fault
81d3a0b26c	x86emul: limit-check branch targets
Please indicate any further commits you think need putting in
before that stable release (Stefano, I'd in particular rely on you
to indicate any possible ARM candidates).

Thanks, Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: 4.5.3 preparations

[Lars Kurth]

We should make sure that all relevant security patches are included
Thanks for the heads-up
Lars

> On 29 Feb 2016, at 10:55, Jan Beulich <jbeulich@suse.com> wrote:
> 
> All,
> 
> it just occurred to me that 4.5.2 has been a while back, and indeed
> 4.5.3 would be due later this week. This may be a little too eager,
> but I'd like to aim at getting this out at least some time next week.
> Besides what is in the tree already, I have three more commits I
> intend to backport:
> 0640ffb67f	x86emul: fix rIP handling
> 1329105943	x86/hvm: print register state upon triple fault
> 81d3a0b26c	x86emul: limit-check branch targets
> Please indicate any further commits you think need putting in
> before that stable release (Stefano, I'd in particular rely on you
> to indicate any possible ARM candidates).
> 
> Thanks, Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Call for tools backport requests for 4.5.x (Re: 4.5.3 preparations)

[Ian Jackson]

Jan Beulich writes ("4.5.3 preparations"):
> it just occurred to me that 4.5.2 has been a while back, and indeed
> 4.5.3 would be due later this week. This may be a little too eager,
> but I'd like to aim at getting this out at least some time next week.
> Besides what is in the tree already, I have three more commits I
> intend to backport:

I have cleared out my current backport list.

For reference, I don't do a sweep of the git log of master to look for
things to backport.

I rely on someone (which might be the maintainer or submitter, or
anyone else) noticing that a fix ought to be considered for backport
and bringing it to my attention.

My backport queue was surprisingly empty.  I encourage people to reply
to this message with backport requets.

Thanks,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Call for tools backport requests for 4.5.x (Re: 4.5.3 preparations)

[Olaf Hering]

On Mon, Feb 29, Ian Jackson wrote:

> I rely on someone (which might be the maintainer or submitter, or
> anyone else) noticing that a fix ought to be considered for backport
> and bringing it to my attention.

I propose this build fix:
77fec3a tools/console: correct make dependencies for _paths.h

Olaf

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Call for tools backport requests for 4.5.x (Re: 4.5.3 preparations)

[Olaf Hering]

On Mon, Feb 29, Olaf Hering wrote:

> 77fec3a tools/console: correct make dependencies for _paths.h

Sorry, I read the Subject as 4.6.x ...

Olaf

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Call for tools backport requests for 4.5.x (Re: 4.5.3 preparations)

[Ian Jackson]

Olaf Hering writes ("Re: [Xen-devel] Call for tools backport requests for 4.5.x (Re: 4.5.3 preparations)"):
> On Mon, Feb 29, Ian Jackson wrote:
> 
> > I rely on someone (which might be the maintainer or submitter, or
> > anyone else) noticing that a fix ought to be considered for backport
> > and bringing it to my attention.
> 
> I propose this build fix:
> 77fec3a tools/console: correct make dependencies for _paths.h

Thanks, applied to 4.6.  It didn't apply cleanly to 4.5.  If 4.5 has
the same bug I would welcome a backport.

Thanks,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Call for tools backport requests for 4.5.x (Re: 4.5.3 preparations)

[Ian Jackson]

Olaf Hering writes ("Re: [Xen-devel] Call for tools backport requests for 4.5.x (Re: 4.5.3 preparations)"):
> On Mon, Feb 29, Olaf Hering wrote:
> > 77fec3a tools/console: correct make dependencies for _paths.h
> 
> Sorry, I read the Subject as 4.6.x ...

Right.  Well, actually, I'm happy right now to take backport requests
for all the maintained trees.

Thanks,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: 4.5.3 preparations

[Stefano Stabellini]

On Mon, 29 Feb 2016, Jan Beulich wrote:
> All,
> 
> it just occurred to me that 4.5.2 has been a while back, and indeed
> 4.5.3 would be due later this week. This may be a little too eager,
> but I'd like to aim at getting this out at least some time next week.
> Besides what is in the tree already, I have three more commits I
> intend to backport:
> 0640ffb67f	x86emul: fix rIP handling
> 1329105943	x86/hvm: print register state upon triple fault
> 81d3a0b26c	x86emul: limit-check branch targets
> Please indicate any further commits you think need putting in
> before that stable release (Stefano, I'd in particular rely on you
> to indicate any possible ARM candidates).
 
93f67ce718a020686d98db7edd7e9298bd7b36a5  xen/arm: vgic-v2: Report the correct GICC size to the guest
70ed1226d2e27f43c6f7d3aa9d5f2a0e1b29347d  xen/arm: vgic-v2: Implement correctly ITARGETSR0 - ITARGETSR7 read-only

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: 4.5.3 preparations

[Jan Beulich]

>>> On 01.03.16 at 16:44, <stefano.stabellini@eu.citrix.com> wrote:
> On Mon, 29 Feb 2016, Jan Beulich wrote:
>> All,
>> 
>> it just occurred to me that 4.5.2 has been a while back, and indeed
>> 4.5.3 would be due later this week. This may be a little too eager,
>> but I'd like to aim at getting this out at least some time next week.
>> Besides what is in the tree already, I have three more commits I
>> intend to backport:
>> 0640ffb67f	x86emul: fix rIP handling
>> 1329105943	x86/hvm: print register state upon triple fault
>> 81d3a0b26c	x86emul: limit-check branch targets
>> Please indicate any further commits you think need putting in
>> before that stable release (Stefano, I'd in particular rely on you
>> to indicate any possible ARM candidates).
>  
> 93f67ce718a020686d98db7edd7e9298bd7b36a5  xen/arm: vgic-v2: Report the 
> correct GICC size to the guest
> 70ed1226d2e27f43c6f7d3aa9d5f2a0e1b29347d  xen/arm: vgic-v2: Implement 
> correctly ITARGETSR0 - ITARGETSR7 read-only

Will do. I'm puzzled that they're in 4.6.1, but didn't at the
same time go into staging-4.5.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: 4.5.3 preparations

[Stefano Stabellini]

On Tue, 1 Mar 2016, Jan Beulich wrote:
> >>> On 01.03.16 at 16:44, <stefano.stabellini@eu.citrix.com> wrote:
> > On Mon, 29 Feb 2016, Jan Beulich wrote:
> >> All,
> >> 
> >> it just occurred to me that 4.5.2 has been a while back, and indeed
> >> 4.5.3 would be due later this week. This may be a little too eager,
> >> but I'd like to aim at getting this out at least some time next week.
> >> Besides what is in the tree already, I have three more commits I
> >> intend to backport:
> >> 0640ffb67f	x86emul: fix rIP handling
> >> 1329105943	x86/hvm: print register state upon triple fault
> >> 81d3a0b26c	x86emul: limit-check branch targets
> >> Please indicate any further commits you think need putting in
> >> before that stable release (Stefano, I'd in particular rely on you
> >> to indicate any possible ARM candidates).
> >  
> > 93f67ce718a020686d98db7edd7e9298bd7b36a5  xen/arm: vgic-v2: Report the 
> > correct GICC size to the guest
> > 70ed1226d2e27f43c6f7d3aa9d5f2a0e1b29347d  xen/arm: vgic-v2: Implement 
> > correctly ITARGETSR0 - ITARGETSR7 read-only
> 
> Will do. I'm puzzled that they're in 4.6.1, but didn't at the
> same time go into staging-4.5.
 
Indeed, that's why they were easy to spot

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: 4.5.3 preparations

[M A Young]

On Mon, 29 Feb 2016, Jan Beulich wrote:

> All,
> 
> it just occurred to me that 4.5.2 has been a while back, and indeed
> 4.5.3 would be due later this week. This may be a little too eager,
> but I'd like to aim at getting this out at least some time next week.
> Besides what is in the tree already, I have three more commits I
> intend to backport:
> 0640ffb67f	x86emul: fix rIP handling
> 1329105943	x86/hvm: print register state upon triple fault
> 81d3a0b26c	x86emul: limit-check branch targets
> Please indicate any further commits you think need putting in
> before that stable release (Stefano, I'd in particular rely on you
> to indicate any possible ARM candidates).

I believe the current 4.5 trees are missing
xsa155-xen-0001-xen-Add-RING_COPY_REQUEST.patch
xsa155-xen-0002-blktap2-Use-RING_COPY_REQUEST.patch
xsa155-xen-0003-libvchan-Read-prod-cons-only-once.patch
xsa164.patch

	Michael Young

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: 4.5.3 preparations

[Jan Beulich]

>>> On 01.03.16 at 23:43, <m.a.young@durham.ac.uk> wrote:
> On Mon, 29 Feb 2016, Jan Beulich wrote:
>> it just occurred to me that 4.5.2 has been a while back, and indeed
>> 4.5.3 would be due later this week. This may be a little too eager,
>> but I'd like to aim at getting this out at least some time next week.
>> Besides what is in the tree already, I have three more commits I
>> intend to backport:
>> 0640ffb67f	x86emul: fix rIP handling
>> 1329105943	x86/hvm: print register state upon triple fault
>> 81d3a0b26c	x86emul: limit-check branch targets
>> Please indicate any further commits you think need putting in
>> before that stable release (Stefano, I'd in particular rely on you
>> to indicate any possible ARM candidates).
> 
> I believe the current 4.5 trees are missing
> xsa155-xen-0001-xen-Add-RING_COPY_REQUEST.patch
> xsa155-xen-0002-blktap2-Use-RING_COPY_REQUEST.patch
> xsa155-xen-0003-libvchan-Read-prod-cons-only-once.patch

These indeed appear to be missing (also on other stable
branches) - Ian?

> xsa164.patch

This one I can't seem to see missing - it's the top commit on the
stable-4.5 branch (and the stable-4.6, FWIW). (And FTR I can
also see the qemu-upstream variant of the XSA-162 fix - which
has been missing from 4.4.4 and 4.6.1 - in the respective stable
branches.)

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: 4.5.3 preparations

[M A Young]

On Wed, 2 Mar 2016, Jan Beulich wrote:

> >>> On 01.03.16 at 23:43, <m.a.young@durham.ac.uk> wrote:
> > On Mon, 29 Feb 2016, Jan Beulich wrote:
> >> it just occurred to me that 4.5.2 has been a while back, and indeed
> >> 4.5.3 would be due later this week. This may be a little too eager,
> >> but I'd like to aim at getting this out at least some time next week.
> >> Besides what is in the tree already, I have three more commits I
> >> intend to backport:
> >> 0640ffb67f	x86emul: fix rIP handling
> >> 1329105943	x86/hvm: print register state upon triple fault
> >> 81d3a0b26c	x86emul: limit-check branch targets
> >> Please indicate any further commits you think need putting in
> >> before that stable release (Stefano, I'd in particular rely on you
> >> to indicate any possible ARM candidates).
> > 
> > I believe the current 4.5 trees are missing
> > xsa155-xen-0001-xen-Add-RING_COPY_REQUEST.patch
> > xsa155-xen-0002-blktap2-Use-RING_COPY_REQUEST.patch
> > xsa155-xen-0003-libvchan-Read-prod-cons-only-once.patch
> 
> These indeed appear to be missing (also on other stable
> branches) - Ian?
> 
> > xsa164.patch
> 
> This one I can't seem to see missing - it's the top commit on the
> stable-4.5 branch (and the stable-4.6, FWIW). (And FTR I can
> also see the qemu-upstream variant of the XSA-162 fix - which
> has been missing from 4.4.4 and 4.6.1 - in the respective stable
> branches.)

You are right. I probably took the commit specified in Config.mk in my 
testing rather than the head of the qemu-xen-traditional 4.5 branch.

	Michael Young

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: 4.5.3 preparations

[Jan Beulich]

>>> On 01.03.16 at 16:44, <stefano.stabellini@eu.citrix.com> wrote:
> On Mon, 29 Feb 2016, Jan Beulich wrote:
>> it just occurred to me that 4.5.2 has been a while back, and indeed
>> 4.5.3 would be due later this week. This may be a little too eager,
>> but I'd like to aim at getting this out at least some time next week.
>> Besides what is in the tree already, I have three more commits I
>> intend to backport:
>> 0640ffb67f	x86emul: fix rIP handling
>> 1329105943	x86/hvm: print register state upon triple fault
>> 81d3a0b26c	x86emul: limit-check branch targets
>> Please indicate any further commits you think need putting in
>> before that stable release (Stefano, I'd in particular rely on you
>> to indicate any possible ARM candidates).
>  
> 93f67ce718a020686d98db7edd7e9298bd7b36a5  xen/arm: vgic-v2: Report the 
> correct GICC size to the guest
> 70ed1226d2e27f43c6f7d3aa9d5f2a0e1b29347d  xen/arm: vgic-v2: Implement 
> correctly ITARGETSR0 - ITARGETSR7 read-only

Done. In the process of doing so I've got the impression that you
actually handed my commit IDs from the 4.6 branch instead of
master ones. Also the second one didn't apply without fuzz, so
please double check.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel