From: Andrew Morton <akpm@linux-foundation.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Matt Mackall <mpm@selenic.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Dave Airlie <airlied@redhat.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH] drm: Prune GEM vma entries
Date: Mon, 27 Sep 2010 13:08:44 -0700 [thread overview]
Message-ID: <20100927130844.b57ee9eb.akpm@linux-foundation.org> (raw)
In-Reply-To: <1285618116-10086-1-git-send-email-chris@chris-wilson.co.uk>
That was quick, thanks.
On Mon, 27 Sep 2010 21:08:36 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Hook the GEM vm open/close ops into the generic drm vm open/close so
> that the vma entries are created and destroy appropriately.
Please update the changelog to indicate that it fixes a memory leak.
> Reported-by: Matt Mackall <mpm@selenic.com>
> Cc: Dave Airlie <airlied@redhat.com>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
And here please add
Cc: <stable@kernel.org>
so that earlier kernels get reliably fixed.
Thanks.
next prev parent reply other threads:[~2010-09-27 20:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1008221615350.29062@chino.kir.corp.google.com>
[not found] ` <1282623994.10679.921.camel@calx>
[not found] ` <alpine.DEB.2.00.1008232134480.25742@chino.kir.corp.google.com>
[not found] ` <1282663241.10679.958.camel@calx>
[not found] ` <alpine.DEB.2.00.1008241036250.344@router.home>
2010-08-25 20:59 ` DRM-related kmalloc-32 memory leak in 2.6.35 Matt Mackall
2010-09-27 18:52 ` Andrew Morton
2010-09-27 20:08 ` [PATCH] drm: Prune GEM vma entries Chris Wilson
2010-09-27 20:08 ` Andrew Morton [this message]
2010-09-27 20:28 ` Chris Wilson
2010-10-02 0:09 ` Matt Mackall
2010-10-03 18:59 ` Paul Rolland
2010-10-04 7:07 ` Paul Rolland
2010-09-27 20:40 ` DRM-related kmalloc-32 memory leak in 2.6.35 David Rientjes
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=20100927130844.b57ee9eb.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=airlied@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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
Powered by JetHome