From: Florian Mickler <florian@mickler.org>
To: Eric Anholt <eric@anholt.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
jbarnes@virtuousgeek.org, airlied@linux.ie, keithp@keithp.com
Subject: Re: Regression X Hangs at bootup -- PATCH
Date: Wed, 8 Apr 2009 09:41:33 +0200 [thread overview]
Message-ID: <20090408094133.094dae4d@schatten> (raw)
In-Reply-To: <1239158039.19045.6.camel@gaiman.anholt.net>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
On Tue, 07 Apr 2009 19:33:59 -0700
Eric Anholt <eric@anholt.net> wrote:
> On Tue, 2009-04-07 at 22:14 +0200, Florian Mickler wrote:
> > On Tue, 07 Apr 2009 09:21:40 -0700
> > Eric Anholt <eric@anholt.net> wrote:
> >
> >
> > > drm_free's other arguments are unused memory debug leftovers.
> > > I've got a patch I need to push at airlied to remove
> > > drm_malloc/drm_calloc/drm_free.
> > >
> > in that case it is of course a non issue. but would you mind
> > to add a note like 'this adds a memleak to
> > i915_gem_put_relocs_to_user which will be fixed in a followup
> > patch', or just rebase it onto that patch?
>
> Just to be clear, there is no memleak:
>
> /** Wrapper around kfree() */
> static __inline__ void drm_free(void *pt, size_t size, int area)
> {
> kfree(pt);
> }
>
> The arg would only get used if DRM_DEBUG_MEMORY was set, but there's
> no way in the kernel to do so. I don't think anybody's used it in
> years, and I'm sure there would be broken drm_free arguments since
> it's untested. It was never very useful even back in the day, since
> most everything ended up lumped under DRM_MEM_DRIVER.
>
wtf? alright :)
thx for clarifying. i should have just looked.
bye,
Florian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-04-08 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 20:55 Regression X Hangs at bootup -- PATCH Florian Mickler
2009-04-07 2:03 ` Eric Anholt
2009-04-07 7:23 ` Florian Mickler
2009-04-07 16:21 ` Eric Anholt
2009-04-07 20:14 ` Florian Mickler
2009-04-08 2:33 ` Eric Anholt
2009-04-08 7:41 ` Florian Mickler [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=20090408094133.094dae4d@schatten \
--to=florian@mickler.org \
--cc=airlied@linux.ie \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.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