From: Dave Jones <davej@redhat.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Dave Airlie <airlied@redhat.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
David Herrmann <dh.herrmann@gmail.com>
Subject: Re: [PATCH] drm: Fix use-after-free in the shadow-attache exit code
Date: Thu, 30 Jan 2014 12:12:54 -0500 [thread overview]
Message-ID: <20140130171254.GA1065@redhat.com> (raw)
In-Reply-To: <1391101118-29633-1-git-send-email-daniel.vetter@ffwll.ch>
On Thu, Jan 30, 2014 at 05:58:38PM +0100, Daniel Vetter wrote:
> This regression has been introduced in
>
> commit b3f2333de8e81b089262b26d52272911523e605f
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date: Wed Dec 11 11:34:31 2013 +0100
>
> drm: restrict the device list for shadow attached drivers
>
btw, I noticed this because it got flagged in the nightly coverity runs.
Of the 18 new issues added yesterday 14 were from drivers/gpu/
If drm developers want to sign up at http://scan.coverity.com
to help out looking over those (and the backlog: stats below)
I can get those accounts approved quickly.
I've been going through trying to clear out as much of the 'noise'
as possible, but it's a huge job. There's a bunch of cases where
the checker can't figure out if it's a real bug or not because
it doesn't know things like "the hardware will only ever return
these values", but the majority look like actual coding flaws.
Dave
Currently outstanding issues:
Radeon: 64
Nouveau: 36
i915: 32
misc drm: 24
gma500: 11
qxl: 7
prev parent reply other threads:[~2014-01-30 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 16:58 [PATCH] drm: Fix use-after-free in the shadow-attache exit code Daniel Vetter
2014-01-30 17:08 ` David Herrmann
2014-01-30 17:12 ` Dave Jones [this message]
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=20140130171254.GA1065@redhat.com \
--to=davej@redhat.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dh.herrmann@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox