[Bug 104760] System hang when use glTexImage3D to specify a 3D texture image

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=104760

Eero Tamminen <eero.t.tamminen at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eero.t.tamminen at intel.com
           See Also|                            |https://bugs.freedesktop.or
                   |                            |g/show_bug.cgi?id=106106,
                   |                            |https://bugs.freedesktop.or
                   |                            |g/show_bug.cgi?id=106136
           Keywords|                            |security

--- Comment #28 from Eero Tamminen <eero.t.tamminen at intel.com> ---
(In reply to Mark Janes from comment #26)
> Is the correct resolution to track graphics memory in a way that allows the
> OOM killer to target the process that is locking up the system?

GFX memory usage tracking isn't just an Intel or 3D specific issue, it's an
issue for the whole kernel DRI subsystem.

There's even a CVE about it: https://nvd.nist.gov/vuln/detail/CVE-2013-7445


> Lionel's workaround will handle this particular case, but there are many
> other ways to produce the same effect.

See also bug 106106 and bug 106136.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190212/1085a2e4/attachment.html>