Re: [Mesa-dev] [PATCH] main/getteximage: Take y-offset into account for memcpy size

2016-11-22 Thread Jason Ekstrand
On Nov 22, 2016 11:03, "Eduardo Lima Mitev" wrote: > > On 11/22/2016 06:43 PM, Jason Ekstrand wrote: > > On Tue, Nov 22, 2016 at 9:11 AM, Eduardo Lima Mitev > > wrote: > > > > In get_tex_memcpy, when copying texture data directly from source > > to destination (wh

Re: [Mesa-dev] [PATCH] main/getteximage: Take y-offset into account for memcpy size

2016-11-22 Thread Eduardo Lima Mitev
On 11/22/2016 06:43 PM, Jason Ekstrand wrote: > On Tue, Nov 22, 2016 at 9:11 AM, Eduardo Lima Mitev > wrote: > > In get_tex_memcpy, when copying texture data directly from source > to destination (when row strides match for both src and dst), the > block size

Re: [Mesa-dev] [PATCH] main/getteximage: Take y-offset into account for memcpy size

2016-11-22 Thread Jason Ekstrand
On Tue, Nov 22, 2016 at 9:11 AM, Eduardo Lima Mitev wrote: > In get_tex_memcpy, when copying texture data directly from source > to destination (when row strides match for both src and dst), the > block size is currently calculated as 'bytes-per-row * image-height', > ignoring the given y-offset

[Mesa-dev] [PATCH] main/getteximage: Take y-offset into account for memcpy size

2016-11-22 Thread Eduardo Lima Mitev
In get_tex_memcpy, when copying texture data directly from source to destination (when row strides match for both src and dst), the block size is currently calculated as 'bytes-per-row * image-height', ignoring the given y-offset argument. This can cause a read past the end of the mapped buffer, l