From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102552] Null dereference due to not checking return value of util_format_description
Date: Wed, 06 Sep 2017 21:02:04 +0000 [thread overview]
Message-ID: <bug-102552-502-PlWubqucJH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102552-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 555 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102552
--- Comment #4 from Ilia Mirkin <imirkin@alum.mit.edu> ---
Oh interesting. I think some of those formats were removed recently. I wonder
if such call sites should be fixed. Nouveau calls util_format_is_supported up
high in is_format_supported, I suspect that gets it out of trouble.
Either way, is_format_supported or its callers should be fixed, not utility
functions like util_format_get_first_non_void_channel.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1392 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-09-06 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 19:40 [Bug 102552] Null dereference due to not checking return value of util_format_description bugzilla-daemon
2017-09-05 19:46 ` bugzilla-daemon
2017-09-05 20:43 ` bugzilla-daemon
2017-09-06 19:56 ` bugzilla-daemon
2017-09-06 21:02 ` bugzilla-daemon [this message]
2017-09-07 18:51 ` bugzilla-daemon
2017-09-10 14:25 ` bugzilla-daemon
2017-09-10 14:35 ` bugzilla-daemon
2017-09-12 20:44 ` bugzilla-daemon
2017-09-14 5:19 ` 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-102552-502-PlWubqucJH@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.