From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 38196] New: Null pointer dereference in nouveau_gpuobj_channel_takedown
Date: Sat, 11 Jun 2011 18:11:41 -0700 (PDT) [thread overview]
Message-ID: <bug-38196-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=38196
Summary: Null pointer dereference in
nouveau_gpuobj_channel_takedown
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/DRI/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: rjgleits-Bdlq13kUjeyLZ21kGMrzwg@public.gmane.org
The code for this procedure includes (line 878) assignment to a pointer of type
struct nv50_display_crtc. However nv50_display(dev) is null for earlier cards
(e.g., nv40). This causes a kernel oops if for example a program using mesa is
terminated.
I tried skipping the loop containing this line if nv50_display(dev) is null and
this worked on my 6800 Ultra.
Best Wishes,
Bob Gleitsmann
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-06-12 1:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 1:11 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-38196-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-06-12 2:23 ` [Bug 38196] Null pointer dereference in nouveau_gpuobj_channel_takedown bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-12 8:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-18 13:22 ` 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-38196-8800@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.