From: Gustavo Padovan <gustavo.padovan@collabora.com>
To: Rafael Antognolli <rafael.antognolli@intel.com>
Cc: gustavo.padovan@collabora.co.uk, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] dma-buf/sync_file: Always increment refcount when merging fences.
Date: Tue, 13 Sep 2016 20:41:41 -0300 [thread overview]
Message-ID: <20160913234141.GA11742@joana> (raw)
In-Reply-To: <1473809067-6019-1-git-send-email-rafael.antognolli@intel.com>
Hi Rafael,
2016-09-13 Rafael Antognolli <rafael.antognolli@intel.com>:
> The refcount of a fence should be increased whenever it is added to a merged
> fence, since it will later be decreased when the merged fence is destroyed.
> Failing to do so will cause the original fence to be freed if the merged fence
> gets freed, but other places still referencing won't know about it.
>
> This patch fixes a kernel panic that can be triggered by creating a fence that
> is expired (or increasing the timeline until it expires), then creating a
> merged fence out of it, and deleting the merged fence. This will make the
> original expired fence's refcount go to zero.
>
> Signed-off-by: Rafael Antognolli <rafael.antognolli@intel.com>
> ---
>
> Sample code to trigger the mentioned kernel panic (might need to be executed a
> couple times before it actually breaks everything):
>
> static void test_sync_expired_merge(void)
> {
> int iterations = 1 << 20;
> int timeline;
> int i;
> int fence_expired, fence_merged;
>
> timeline = sw_sync_timeline_create();
>
> sw_sync_timeline_inc(timeline, 100);
> fence_expired = sw_sync_fence_create(timeline, 1);
> fence_merged = sw_sync_merge(fence_expired, fence_expired);
> sw_sync_fence_destroy(fence_merged);
>
> for (i = 0; i < iterations; i++) {
> int fence = sw_sync_merge(fence_expired, fence_expired);
>
> igt_assert_f(sw_sync_wait(fence, -1) > 0,
> "Failure waiting on fence\n");
> sw_sync_fence_destroy(fence);
> }
>
> sw_sync_fence_destroy(fence_expired);
> }
>
> drivers/dma-buf/sync_file.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
Thanks for spotting this.
Reviewed-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Gustavo
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-13 23:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 23:24 [PATCH] dma-buf/sync_file: Always increment refcount when merging fences Rafael Antognolli
2016-09-13 23:41 ` Gustavo Padovan [this message]
2016-09-14 10:05 ` Chris Wilson
2016-09-14 14:04 ` Gustavo Padovan
2016-09-14 15:45 ` Rafael Antognolli
2016-09-14 16:38 ` Gustavo Padovan
2016-09-14 17:57 ` Chris Wilson
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=20160913234141.GA11742@joana \
--to=gustavo.padovan@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=rafael.antognolli@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