public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Don't leak the capture list items
Date: Thu, 9 Dec 2021 17:28:40 +0000	[thread overview]
Message-ID: <c90325d8-acdd-0833-5b24-9d0effa873d1@intel.com> (raw)
In-Reply-To: <20211209141304.393479-1-thomas.hellstrom@linux.intel.com>

On 09/12/2021 14:13, Thomas Hellström wrote:
> When we recently converted the capture code to use vma snapshots,
> we forgot to free the struct i915_capture_list list items after use.
> 
> Fix that by bringing back a kfree.
> 
> Fixes: ff20afc4cee7 ("drm/i915: Update error capture code to avoid using the current vma state")
> Cc: Ramalingam C <ramalingam.c@intel.com>
> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>

  reply	other threads:[~2021-12-09 17:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 14:13 [Intel-gfx] [PATCH] drm/i915: Don't leak the capture list items Thomas Hellström
2021-12-09 17:28 ` Matthew Auld [this message]
2021-12-10  1:41 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2021-12-10 15:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Don't leak the capture list items (rev2) Patchwork
2021-12-11  9:49 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-12-13  9:50   ` Thomas Hellström
2021-12-13 17:22     ` Vudum, Lakshminarayana
2021-12-13 17:10 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork

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=c90325d8-acdd-0833-5b24-9d0effa873d1@intel.com \
    --to=matthew.auld@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=thomas.hellstrom@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