From: zhoucm1 <david1.zhou@amd.com>
To: Grazvydas Ignotas <notasas@gmail.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: fix sched fence slab teardown
Date: Mon, 24 Oct 2016 10:34:43 +0800 [thread overview]
Message-ID: <580D7343.7030701@amd.com> (raw)
In-Reply-To: <1477247507-11378-2-git-send-email-notasas@gmail.com>
Acked-by: Chunming Zhou <david1.zhou@amd.com>
On 2016年10月24日 02:31, Grazvydas Ignotas wrote:
> To free fences, call_rcu() is used, which calls amd_sched_fence_free()
> after a grace period. During teardown, there is no guarantee all
> callbacks have finished, so sched_fence_slab may be destroyed before
> all fences have been freed. If we are lucky, this results in some slab
> warnings, if not, we get a crash in one of rcu threads because callback
> is called after amdgpu has already been unloaded.
>
> Fix it with a rcu_barrier().
>
> Fixes: 189e0fb76304 ("drm/amdgpu: RCU protected amd_sched_fence_release")
> Signed-off-by: Grazvydas Ignotas <notasas@gmail.com>
> ---
> drivers/gpu/drm/amd/scheduler/gpu_scheduler.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c b/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c
> index 963a24d..910b8d5 100644
> --- a/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c
> +++ b/drivers/gpu/drm/amd/scheduler/gpu_scheduler.c
> @@ -645,6 +645,7 @@ void amd_sched_fini(struct amd_gpu_scheduler *sched)
> {
> if (sched->thread)
> kthread_stop(sched->thread);
> + rcu_barrier();
> if (atomic_dec_and_test(&sched_fence_slab_ref))
> kmem_cache_destroy(sched_fence_slab);
> }
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-10-24 2:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 18:31 [PATCH] drm/amdgpu: fix sched fence slab teardown Grazvydas Ignotas
2016-10-24 2:34 ` zhoucm1 [this message]
2016-10-24 9:06 ` Christian König
[not found] ` <bde776d0-0044-5742-ae1a-1de2a4cf5faa-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2016-10-24 16:08 ` Alex Deucher
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=580D7343.7030701@amd.com \
--to=david1.zhou@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=notasas@gmail.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 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.