Chris Wilson b5e0a9418e drm/i915: Set fake_vma.size as well as fake_vma.node.size for capture
When capturing the bo, we allocate an error object with an array of
min(vma->size, vma->node.size) pages, plus a bit for compression overhead.
However, when creating the fake vma to describe the bo, only one of the
sizes was filled in, resulting in a too small array. Through my and CI
testing, this was sufficient for the mostly empty NULL context as
it compressed well (or the out-of-bounds access simply didn't cause an
issue). However, in real workloads on Cannonlake, we were overflowing
that array and causing havoc with the random memory corruption.

Reported-by: Rafael Antognolli <rafael.antognolli@intel.com>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103964
Fixes: 4e90a6e22272 ("drm/i915: Record default HW state in the GPU error state")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Tested-by: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20171201001536.13941-1-chris@chris-wilson.co.uk
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
2017-12-01 09:17:04 +00:00
..
2017-08-09 22:43:50 -07:00
2017-11-02 12:40:41 +10:00
2017-10-07 13:17:07 +02:00
2017-09-05 11:08:17 -07:00
2017-11-02 12:40:41 +10:00
2017-09-10 20:40:00 -07:00
2017-10-15 07:50:38 -04:00
2017-08-29 13:46:35 +02:00
2017-09-05 11:08:17 -07:00
2017-08-22 11:04:51 -07:00
2017-09-11 13:04:32 -07:00
2017-11-02 12:40:41 +10:00
2017-09-13 10:56:00 -07:00
2017-10-28 10:46:20 -07:00
2017-10-28 10:46:20 -07:00
2017-11-02 12:40:41 +10:00
2017-09-05 12:45:03 -07:00
2017-08-30 14:03:42 -06:00
2017-09-14 13:33:33 -07:00
2017-09-07 21:11:05 -07:00
2017-10-27 20:41:05 -07:00
2017-08-24 09:57:28 +02:00