From: Daniel Vetter <daniel@ffwll.ch>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] [REGRESSION] component: add support for releasing match data
Date: Tue, 26 Jan 2016 17:26:07 +0100 [thread overview]
Message-ID: <20160126162607.GC11240@phenom.ffwll.local> (raw)
In-Reply-To: <56A79CF2.4010200@linux.intel.com>
On Tue, Jan 26, 2016 at 05:21:06PM +0100, Maarten Lankhorst wrote:
> Op 26-01-16 om 15:48 schreef Russell King - ARM Linux:
> > On Tue, Jan 26, 2016 at 03:28:34PM +0100, Maarten Lankhorst wrote:
> >> Something similar to a segfault. It's trying to call 0x6b6b6b6b6b which
> >> is POISON_FREE.
> >>
> >> mc appears to be freed already, so calling mc->release would jump to
> >> invalid data.
> > It seems that my devm foo wasn't quite up to scratch. Quite why it
> > doesn't show here while testing it (I have patches for the etnaviv
> > GPU driver, which I'm regularly inserting/removing) I'm not sure.
> >
> > Please test this patch - it seems "no worse" for me (in that it didn't
> > crash before, and it still doesn't crash.)
> That one works, thanks. :)
Awesome, applied to the CI-only topic branch to unblock the robots, will
fall out automatically once the proper patch lands upstream.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2016-01-26 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 13:42 [REGRESSION] component: add support for releasing match data Maarten Lankhorst
2016-01-26 14:15 ` Russell King - ARM Linux
2016-01-26 14:28 ` Maarten Lankhorst
2016-01-26 14:48 ` Russell King - ARM Linux
2016-01-26 16:21 ` Maarten Lankhorst
2016-01-26 16:26 ` Daniel Vetter [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=20160126162607.GC11240@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=maarten.lankhorst@linux.intel.com \
/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