<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [ILK i386 Bisected]X start fail" href="https://bugs.freedesktop.org/show_bug.cgi?id=86679#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [ILK i386 Bisected]X start fail" href="https://bugs.freedesktop.org/show_bug.cgi?id=86679">bug 86679</a> from <a class="email" href="mailto:ugis.germanis@gmail.com" title="Ugis Germanis <ugis.germanis@gmail.com>"> Ugis Germanis</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=86679#c15">comment #15</a>) > (In reply to Jani Nikula from <a href="show_bug.cgi?id=86679#c14">comment #14</a>) > > Regresses here and there, time for a revert? > > Revert of what? You have already applied the "fix" from Daniel to ban the > pin ioctl completely. This bug is about userspace being able to oops the > kernel by feeding it a malicious mode. <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Intel GM45 graphics glitches with Kernel 3.18.0" href="show_bug.cgi?id=87279">Bug 87279</a> is about corruption in the > ddx using sw fallbacks, and <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - [ILK bisected] 3.18 black screen after boot" href="show_bug.cgi?id=87330">bug 87330</a> has not been analysed to find the > actual root cause. drm-i915-Disallow-pin-ioctl-completely-for-kms-drive seems to fix <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Intel GM45 graphics glitches with Kernel 3.18.0" href="show_bug.cgi?id=87279">https://bugs.freedesktop.org/show_bug.cgi?id=87279</a> bug aswell, which has been marked as a duplicate of this bug</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>