[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: [PATCH 2 of 3] xentrace: use tbuf_size for overflow check



On Fri, Apr 01, George Dunlap wrote:

> On Wed, 2011-03-30 at 19:04 +0100, Olaf Hering wrote:

> > xentrace: use tbuf_size for overflow check
> > 
> > The calculated number of per-cpu trace pages is stored in t_info and
> > shared with tools like xentrace. Since its an u16 the value may overflow
> > because the current check is based on u32.
> 
> Hmm -- while this is true, it's possible this may change in the future.
> If we ever changed t_info.tbuf_size to be u32, then t_buf.prod/cons
> would again be the limiting factor.
> 
> Should we perhaps add both checks?

I will update the patch to check for both.


> > Using the u16 means each cpu could in theory use up to 256MB as trace
> > buffer. However such a large allocation will currently fail on x86 due
> > to the MAX_ORDER limit.
> 
> FWIW, I don't believe that there's any reason the allocations have to be
> contiguous any more.  I kept them contiguous to minimize the changes to
> the moving parts near a release.  But the new system has been pretty
> well tested now, so I think looking at non-contiguous allocations may be
> worthwhile.

This will be a bigger change I think. Added to my todo list.


Olaf

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.