All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-111415-502-PiXfed4eXz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111415-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 871 bytes --]

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

--- Comment #1 from Tom Seewald <tseewald@gmail.com> ---
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=204181

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 experiencing,
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=amd-staging-drm-next&id=a4f6a4c7de97335f3452229e67521eae338af10e

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1972 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-08-18 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-18  4:36 [Bug 111415] BUG: kernel NULL pointer dereference - supervisor read access in kernel mode bugzilla-daemon
2019-08-18 20:53 ` bugzilla-daemon [this message]
2019-10-03  4:14 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-111415-502-PiXfed4eXz@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.