From: John Harrison <john.c.harrison@intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
<intel-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix syncmap memory leak
Date: Fri, 6 Aug 2021 11:23:06 -0700 [thread overview]
Message-ID: <de37e95c-b3e1-0479-db7e-e820077beaa3@intel.com> (raw)
In-Reply-To: <20210730195342.110234-1-matthew.brost@intel.com>
On 7/30/2021 12:53, Matthew Brost wrote:
> A small race exists between intel_gt_retire_requests_timeout and
> intel_timeline_exit which could result in the syncmap not getting
> free'd. Rather than work to hard to seal this race, simply cleanup the
free'd -> freed
> syncmap on fini.
>
> unreferenced object 0xffff88813bc53b18 (size 96):
> comm "gem_close_race", pid 5410, jiffies 4294917818 (age 1105.600s)
> hex dump (first 32 bytes):
> 01 00 00 00 00 00 00 00 00 00 00 00 0a 00 00 00 ................
> 00 00 00 00 00 00 00 00 6b 6b 6b 6b 06 00 00 00 ........kkkk....
> backtrace:
> [<00000000120b863a>] __sync_alloc_leaf+0x1e/0x40 [i915]
> [<00000000042f6959>] __sync_set+0x1bb/0x240 [i915]
> [<0000000090f0e90f>] i915_request_await_dma_fence+0x1c7/0x400 [i915]
> [<0000000056a48219>] i915_request_await_object+0x222/0x360 [i915]
> [<00000000aaac4ee3>] i915_gem_do_execbuffer+0x1bd0/0x2250 [i915]
> [<000000003c9d830f>] i915_gem_execbuffer2_ioctl+0x405/0xce0 [i915]
> [<00000000fd7a8e68>] drm_ioctl_kernel+0xb0/0xf0 [drm]
> [<00000000e721ee87>] drm_ioctl+0x305/0x3c0 [drm]
> [<000000008b0d8986>] __x64_sys_ioctl+0x71/0xb0
> [<0000000076c362a4>] do_syscall_64+0x33/0x80
> [<00000000eb7a4831>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> Fixes: 531958f6f357 ("drm/i915/gt: Track timeline activeness in enter/exit")
> Cc: <stable@vger.kernel.org>
> ---
> drivers/gpu/drm/i915/gt/intel_timeline.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_timeline.c b/drivers/gpu/drm/i915/gt/intel_timeline.c
> index c4a126c8caef..1257f4f11e66 100644
> --- a/drivers/gpu/drm/i915/gt/intel_timeline.c
> +++ b/drivers/gpu/drm/i915/gt/intel_timeline.c
> @@ -127,6 +127,15 @@ static void intel_timeline_fini(struct rcu_head *rcu)
>
> i915_vma_put(timeline->hwsp_ggtt);
> i915_active_fini(&timeline->active);
> +
> + /*
> + * A small race exists between intel_gt_retire_requests_timeout and
> + * intel_timeline_exit which could result in the syncmap not getting
> + * free'd. Rather than work to hard to seal this race, simply cleanup
> + * the syncmap on fini.
What is the race? I'm going round in circles just trying to work out how
intel_gt_retire_requests_timeout is supposed to get to
intel_timeline_exit in the first place.
Also, free'd -> freed.
John.
> + */
> + i915_syncmap_free(&timeline->sync);
> +
> kfree(timeline);
> }
>
next prev parent reply other threads:[~2021-08-06 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 19:53 [Intel-gfx] [PATCH] drm/i915: Fix syncmap memory leak Matthew Brost
2021-07-30 20:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-07-31 2:17 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-08-06 18:23 ` John Harrison [this message]
2021-08-06 18:29 ` [Intel-gfx] [PATCH] " Matthew Brost
2021-08-06 20:16 ` John Harrison
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=de37e95c-b3e1-0479-db7e-e820077beaa3@intel.com \
--to=john.c.harrison@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.brost@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