Re: [Intel-gfx] [PATCH] drm/i915: Fix vmap_batch page iterator overrun

2015-03-13 Thread shuang . he
Tested-By: PRC QA PRTS (Patch Regression Test System Contact: shuang...@intel.com) Task id: 5947 -Summary- Platform Delta drm-intel-nightly Series Applied PNV 276/276

Re: [Intel-gfx] [PATCH] drm/i915: Fix vmap_batch page iterator overrun

2015-03-13 Thread Daniel Vetter
On Fri, Mar 13, 2015 at 02:05:46PM +, Chris Wilson wrote: > On Fri, Mar 13, 2015 at 03:21:53PM +0200, Mika Kuoppala wrote: > > vmap_batch() calculates amount of needed pages for the mapping > > we are going to create. And it uses this page count as an > > argument for the for_each_sg_pages() ma

Re: [Intel-gfx] [PATCH] drm/i915: Fix vmap_batch page iterator overrun

2015-03-13 Thread Chris Wilson
On Fri, Mar 13, 2015 at 03:21:53PM +0200, Mika Kuoppala wrote: > vmap_batch() calculates amount of needed pages for the mapping > we are going to create. And it uses this page count as an > argument for the for_each_sg_pages() macro. The macro takes the number > of sg list entities as an argument,

Re: [Intel-gfx] [PATCH] drm/i915: Fix vmap_batch page iterator overrun

2015-03-13 Thread Tvrtko Ursulin
On 03/13/2015 01:21 PM, Mika Kuoppala wrote: vmap_batch() calculates amount of needed pages for the mapping we are going to create. And it uses this page count as an argument for the for_each_sg_pages() macro. The macro takes the number of sg list entities as an argument, not the page count. So

[Intel-gfx] [PATCH] drm/i915: Fix vmap_batch page iterator overrun

2015-03-13 Thread Mika Kuoppala
vmap_batch() calculates amount of needed pages for the mapping we are going to create. And it uses this page count as an argument for the for_each_sg_pages() macro. The macro takes the number of sg list entities as an argument, not the page count. So we ended up iterating through all the pages on t