All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 106994] [PATCH] Fix null pointer dereference in drmmode_output_dpms
Date: Thu, 21 Jun 2018 15:42:22 +0000	[thread overview]
Message-ID: <bug-106994-8800-2PgDXMZOR5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106994-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #3 from John Lindgren <john-ytntcHzVV1kcWVvVuXF20w@public.gmane.org> ---
Ilia, I tested your tree and it behaves as you expected -- it fixes the crash
on undocking (I see that it adds the same koutput == NULL check) but doesn't
find the external displays on docking again.  I'm not sure what further
information you want me to provide.

I understand that you would like to finish the larger project and get external
DP displays working 100%, but is there any reason why we couldn't start by
committing the koutput == NULL check to fix the crash?

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2018-06-21 15:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21 14:54 [Bug 106994] New: [PATCH] Fix null pointer dereference in drmmode_output_dpms bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-106994-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-06-21 14:55   ` [Bug 106994] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-21 15:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-21 15:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-06-21 15:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-21 16:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-21 16:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-06-21 16:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-09-07 14:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-10-09  4:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-106994-8800-2PgDXMZOR5@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.