<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - forced EDID's can cause a amdgpu to null ptr deref"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100375#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - forced EDID's can cause a amdgpu to null ptr deref"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100375">bug 100375</a>
from <span class="vcard"><a class="email" href="mailto:funfunctor@folklore1984.net" title="Edward O'Callaghan <funfunctor@folklore1984.net>"> <span class="fn">Edward O'Callaghan</span></a>
</span></b>
<pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=100375#c1">comment #1</a>)
<span class="quote">> set_root doesn't look directly related to amdgpu or drm, so this could be
> memory corruption. KASAN might give more information.
>
> Does this only happen when forcing an invalid EDID?</span >
Hi Michel,
yes it only happens on shutdown with a EDID blob passed at boot. Actually the
EDID blob passed I don't think is invalid, I don't know where it is getting the
one in the trace from that could be from perhaps the monitor itself.
Is the kernel there trying to open the EDID blob on a umounted fs?</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>