WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] [PATCH] Fix vulnerability of copy_to_user in PAL em

Quoting Alex Williamson <alex.williamson@xxxxxx>:

>
> On Wed, 2007-12-12 at 07:17 +0100, Tristan Gingold wrote:
> > My latest idea on this subject:
> >
> > The buffers are small: 64 bytes.  So, instead of passing a buffer address,
> > return the buffer by register (using scratch register r14-r21).  The PAL
> > stub can then save it to memory.  I think this approach is the simplest
> > one.
>
>    PAL_BRAND_INFO takes 128 bytes, but probably still feasible.
Right!
Furthermore as PAL_BRAND_INFO is stacked convention we can fully use xencomm
by allocating the buffer on the stack.

Tristan.

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel