Xen devel - Sep 2012 - [PATCH 00/11] various tmem adjustments (mostly XSA-15 related)

01: tmem: only allow tmem control operations from privileged domains
02: tmem: consistently make pool_id a uint32_t
03: tmem: check the pool_id is valid when destroying a tmem pool
04: tmem: check for a valid client ("domain") in the save subops
05: tmem: don''t access guest memory without using the accessors
intended for this
06: tmem: detect arithmetic overflow in tmh_copy_{from,to}_client()
07: tmem: properly drop lock on error path in do_tmem_get()
08: tmem: properly drop lock on error path in do_tmem_op()
09: tmem: reduce severity of log messages
10: tmem: fixup 2010 cleanup patch that breaks tmem save/restore
11: tmem: cleanup

> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: Wednesday, September 05, 2012 6:33 AM
> To: xen-devel
> Cc: Dan Magenheimer; Zhenzhong Duan
> Subject: [PATCH 00/11] various tmem adjustments (mostly XSA-15 related)
> 
> 01: tmem: only allow tmem control operations from privileged domains
> 02: tmem: consistently make pool_id a uint32_t
> 03: tmem: check the pool_id is valid when destroying a tmem pool
> 04: tmem: check for a valid client ("domain") in the save subops
> 05: tmem: don''t access guest memory without using the accessors
intended for this
> 06: tmem: detect arithmetic overflow in tmh_copy_{from,to}_client()
> 07: tmem: properly drop lock on error path in do_tmem_get()
> 08: tmem: properly drop lock on error path in do_tmem_op()
> 09: tmem: reduce severity of log messages
> 10: tmem: fixup 2010 cleanup patch that breaks tmem save/restore
> 11: tmem: cleanup
Thanks Jan and Ian for providing these patches!

Summary: All not already acked by me will be acked by me individually
shortly (with original cc list).  Some comments on PATCH 5/11 but still acked.

Keir or Jan (or whoever is applying the patches), a heads-up would
be appreciated to me and this cc list when this patchset is applied
to -staging or any other Xen tree.

Thanks,
Dan

>>> On 05.09.12 at 18:37, Dan Magenheimer
<dan.magenheimer@oracle.com> wrote:
> Keir or Jan (or whoever is applying the patches), a heads-up would
> be appreciated to me and this cc list when this patchset is applied
> to -staging or any other Xen tree.
It was decided to put them in only after branching off 4.2, so
if all goes well early next week. Backporting to 4.2 would be
considered mostly based upon the whole feature becoming
fully functional again.

Jan

On Thu, Sep 06, 2012 at 12:12:17PM +0100, Jan Beulich
wrote:
> >>> On 05.09.12 at 18:37, Dan Magenheimer
<dan.magenheimer@oracle.com> wrote:
> > Keir or Jan (or whoever is applying the patches), a heads-up would
> > be appreciated to me and this cc list when this patchset is applied
> > to -staging or any other Xen tree.
> 
> It was decided to put them in only after branching off 4.2, so
> if all goes well early next week. Backporting to 4.2 would be
> considered mostly based upon the whole feature becoming
> fully functional again.
That is the goal of course. I am reading this as saying that you want
to wait until we have all of the patches to make it work right - and
then backport in Xen 4.2-stable all at once.

And I believe Dan is narrowing the last of the xm save/restore
ones.
> 
> Jan