From: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ben Skeggs <skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/nouveau: fix nouveau_mm/nouveau_mm_node leak
Date: Mon, 22 Oct 2012 00:19:35 +0200 [thread overview]
Message-ID: <20121021221935.GA2925@joi.lan> (raw)
In-Reply-To: <20121019060514.GA11173-6RkuLLNOGXsZ315U/fw+0NvLeJWuRmrY@public.gmane.org>
On Fri, Oct 19, 2012 at 04:05:14PM +1000, Ben Skeggs wrote:
> On Thu, Oct 11, 2012 at 11:53:09PM +0200, Marcin Slusarz wrote:
> > Signed-off-by: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > ---
> > drivers/gpu/drm/nouveau/core/core/gpuobj.c | 6 +++++-
> > drivers/gpu/drm/nouveau/core/include/core/gpuobj.h | 3 +++
> > 2 files changed, 8 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/nouveau/core/core/gpuobj.c b/drivers/gpu/drm/nouveau/core/core/gpuobj.c
> > index c2a7608..48121d2 100644
> > --- a/drivers/gpu/drm/nouveau/core/core/gpuobj.c
> > +++ b/drivers/gpu/drm/nouveau/core/core/gpuobj.c
> > @@ -39,8 +39,11 @@ nouveau_gpuobj_destroy(struct nouveau_gpuobj *gpuobj)
> > nv_wo32(gpuobj, i, 0x00000000);
> > }
> >
> > + if (gpuobj->node)
> > + nouveau_mm_free(gpuobj->node_heap, &gpuobj->node);
> > +
> if (gpuobj->node) {
> nouveau_mm_free(&nv_gpuobj(gpuobj->parent)->heap,
> &gpuobj->node);
> }
>
> Or something to that effect, instead of having to store the heap
> pointer again.
Oh, right.
(Somehow I assumed pargpu to be different object than parent when
I first read it.)
> > if (gpuobj->heap.block_size)
> > - nouveau_mm_fini(&gpuobj->heap);
> > + WARN_ON(nouveau_mm_fini(&gpuobj->heap));
> Alright, I get this. However, perhaps we should go the full hog here
> and make nouveau_mm_fini() directly do the WARN_ON() in this situation?
>
> There was, once upon a time, reasons for it not doing this, I don't
> believe they're valid anymore though.
OK.
Marcin
next prev parent reply other threads:[~2012-10-21 22:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 21:53 [PATCH] drm/nouveau: fix nouveau_mm/nouveau_mm_node leak Marcin Slusarz
[not found] ` <20121011215309.GA3511-OI9uyE9O0yo@public.gmane.org>
2012-10-16 21:41 ` Marcin Slusarz
2012-10-19 6:05 ` Ben Skeggs
[not found] ` <20121019060514.GA11173-6RkuLLNOGXsZ315U/fw+0NvLeJWuRmrY@public.gmane.org>
2012-10-21 22:19 ` Marcin Slusarz [this message]
[not found] ` <20121021221935.GA2925-OI9uyE9O0yo@public.gmane.org>
2012-10-21 22:43 ` Ben Skeggs
2012-10-21 22:20 ` [PATCH v2] " Marcin Slusarz
2012-10-21 22:21 ` [PATCH] drm/nouveau: warn when trying to free mm which is still in use Marcin Slusarz
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=20121021221935.GA2925@joi.lan \
--to=marcin.slusarz-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=skeggsb-Re5JQEeQqe8AvxtiuMwx3w@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.