On Fri, Mar 31, 2017 at 12:56:40PM +0100, Tvrtko Ursulin wrote: > Userspace WARN was the trigger, but real motive is making sure page > count overflow protection remains in place. Ensuring obj->base.size > matches the backing store and there is no possibility of having an > VMA larger than the object and so either corruption or reading > foreign data. Or maybe some other fails along the way as well. Just to say: we do have VMA both larger and smaller than the object, even ones the same size! I regard the kselftests as better means to really probe internal corner cases, but will never disregard any test for what it tells us about the system and what it may find that no other test might. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
