Closed yanko-yankulov closed 7 years ago
I can trigger a similar panic in both drm-next and HEAD by running one of the WebGL examples. Kostik doesn't appear to have any idea how to fix as I reported it six months ago.
Wow. OK. Thanks.
Hi @mattmacy,
Kib has committed the fix for this to master (568d99bbad1b295d9476cbbc4f8b5cb83e0a7973).
I have one more question on this one though. The reason why we are hitting the upstream bug, and the rest of the system does not, is that MAP_SHARED mappings usually get MAP_PREFAULT_PARTIAL flag, and we don't add it the call to vm_map_find from i915_gem_mmap_ioctl. With prefault_partial hitting the underlying bug, while not impossible, gets pretty hard.
This got me thinking do we have some particular reason to not want the prefaulting there? I couldn't come up with a reason why we wouldn't , so just dropping the question.
Thanks, Yanko
Hi all,
I stumbled on the following panic on drm-next (3025e6199432c5748973776e322a207b8f39b200), again playing with intel-gpu-tests. Providing a reduced test case below ( as the intel test, would not trigger the issue on drm-next. It does with a patch implementing #117 ). The reduced test case triggers always on drm-next.
Have no clue what is actually happening. My guess is that is somehow caused by the code in i915_gem_mmap_ioctl, but really no idea for the moment.
Test case to trigger it: