<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102322#c30">Comment # 30</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102322">bug 102322</a>
from <span class="vcard"><a class="email" href="mailto:jb5sgc1n.nya@20mm.eu" title="dwagner <jb5sgc1n.nya@20mm.eu>"> <span class="fn">dwagner</span></a>
</span></b>
<pre>(In reply to Andrey Grodzovsky from <a href="show_bug.cgi?id=102322#c29">comment #29</a>)
<span class="quote">> > (If that is a Mesa issue, no more than user processes / X11 should have
> > crashed - but not the kernel amdgpu driver... right?)
>
> Not exactly, MESA could create a bad request (faulty GPU address) which
> would lead to this. It can even be triggered on purpose using a debug flag
> from MESA.</span >
My understanding is that all parts of MESA run as user processes, outside of
the kernel space. If such code is allowed to pass parameters into kernel
functions that make the kernel crash, that would be a veritable security hole
which attackers could exploit to stage at least denial-of-service attacks, if
not worse.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>