From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 111415] BUG: kernel NULL pointer dereference - supervisor read access in kernel mode Date: Sun, 18 Aug 2019 20:53:50 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1545918875==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 622F66E05D for ; Sun, 18 Aug 2019 20:53:50 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1545918875== Content-Type: multipart/alternative; boundary="15661616300.b6a368.16048" Content-Transfer-Encoding: 7bit --15661616300.b6a368.16048 Date: Sun, 18 Aug 2019 20:53:50 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D111415 --- Comment #1 from Tom Seewald --- This bug report on the kernel bugtracker appears to be the same or at least= a very similar problem: https://bugzilla.kernel.org/show_bug.cgi?id=3D204181 In that report, Nicholas Kazlauskas posted a possible fix: https://patchwork.freedesktop.org/series/64505/ I have yet to test to see if this patch resolves the crashes I am experienc= ing, but I don't see this as being in the 5.3-rc series, and certainly not in the 5.2 stable releases. Was this fix perhaps overlooked/missed? So far I just see that it is in amd-staging-drm-next as of August 1st: https://cgit.freedesktop.org/~agd5f/linux/commit/?h=3Damd-staging-drm-next&= id=3Da4f6a4c7de97335f3452229e67521eae338af10e --=20 You are receiving this mail because: You are the assignee for the bug.= --15661616300.b6a368.16048 Date: Sun, 18 Aug 2019 20:53:50 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 1 on bug 11141= 5 from Tom Seewald 
This bug report on the kernel bugtracker appears to be the sam=
e or at least a
very similar problem:
https://bu=
gzilla.kernel.org/show_bug.cgi?id=3D204181

In that report, Nicholas Kazlauskas posted a possible fix:
https://patchwo=
rk.freedesktop.org/series/64505/

I have yet to test to see if this patch resolves the crashes I am experienc=
ing,
but I don't see this as being in the 5.3-rc series, and certainly not in the
5.2 stable releases. Was this fix perhaps overlooked/missed?

So far I just see that it is in amd-staging-drm-next as of August 1st:
https://cgit.=
freedesktop.org/~agd5f/linux/commit/?h=3Damd-staging-drm-next&id=3Da4f6=
a4c7de97335f3452229e67521eae338af10e

You are receiving this mail because:
  • You are the assignee for the bug.
= --15661616300.b6a368.16048-- --===============1545918875== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1545918875==--