Re: [Xen-devel] [PATCH] fix potential pa_range_info out of bound access

2016-12-09 Thread Stefano Stabellini
On Fri, 9 Dec 2016, Julien Grall wrote: > Hi Stefano, > > On 09/12/16 01:40, Stefano Stabellini wrote: > > On Thu, 8 Dec 2016, Stefano Stabellini wrote: > > > pa_range_info has only 8 elements and is accessed using pa_range as > > > index. pa_range is initialized to 16, potentially causing out of

Re: [Xen-devel] [PATCH] fix potential pa_range_info out of bound access

2016-12-09 Thread Julien Grall
Hi Stefano, On 09/12/16 01:40, Stefano Stabellini wrote: On Thu, 8 Dec 2016, Stefano Stabellini wrote: pa_range_info has only 8 elements and is accessed using pa_range as index. pa_range is initialized to 16, potentially causing out of bound access errors. Fix the issue by initializing pa_range

Re: [Xen-devel] [PATCH] fix potential pa_range_info out of bound access

2016-12-08 Thread Stefano Stabellini
On Thu, 8 Dec 2016, Stefano Stabellini wrote: > pa_range_info has only 8 elements and is accessed using pa_range as > index. pa_range is initialized to 16, potentially causing out of bound > access errors. Fix the issue by initializing pa_range to the effective > number of pa_range_info elements. >

[Xen-devel] [PATCH] fix potential pa_range_info out of bound access

2016-12-08 Thread Stefano Stabellini
pa_range_info has only 8 elements and is accessed using pa_range as index. pa_range is initialized to 16, potentially causing out of bound access errors. Fix the issue by initializing pa_range to the effective number of pa_range_info elements. CID 1381865 Signed-off-by: Stefano Stabellini diff