From: Qiang Yu <yuq825@gmail.com> To: dri-devel@lists.freedesktop.org Cc: lima@lists.freedesktop.org, "Sumit Semwal" <sumit.semwal@linaro.org>, linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org, "Qiang Yu" <yuq825@gmail.com>, "Christian König" <christian.koenig@amd.com> Subject: [PATCH] dma-buf/resv: fix exclusive fence get Date: Sun, 22 Sep 2019 15:49:00 +0800 [thread overview] Message-ID: <20190922074900.853-1-yuq825@gmail.com> (raw) This causes kernel crash when testing lima driver. Cc: Christian König <christian.koenig@amd.com> Fixes: b8c036dfc66f ("dma-buf: simplify reservation_object_get_fences_rcu a bit") Signed-off-by: Qiang Yu <yuq825@gmail.com> --- drivers/dma-buf/dma-resv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/dma-buf/dma-resv.c b/drivers/dma-buf/dma-resv.c index 42a8f3f11681..709002515550 100644 --- a/drivers/dma-buf/dma-resv.c +++ b/drivers/dma-buf/dma-resv.c @@ -471,7 +471,7 @@ int dma_resv_get_fences_rcu(struct dma_resv *obj, if (pfence_excl) *pfence_excl = fence_excl; else if (fence_excl) - shared[++shared_count] = fence_excl; + shared[shared_count++] = fence_excl; if (!shared_count) { kfree(shared); -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Qiang Yu <yuq825@gmail.com> To: dri-devel@lists.freedesktop.org Cc: lima@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org, "Qiang Yu" <yuq825@gmail.com>, "Christian König" <christian.koenig@amd.com>, linux-media@vger.kernel.org Subject: [PATCH] dma-buf/resv: fix exclusive fence get Date: Sun, 22 Sep 2019 15:49:00 +0800 [thread overview] Message-ID: <20190922074900.853-1-yuq825@gmail.com> (raw) This causes kernel crash when testing lima driver. Cc: Christian König <christian.koenig@amd.com> Fixes: b8c036dfc66f ("dma-buf: simplify reservation_object_get_fences_rcu a bit") Signed-off-by: Qiang Yu <yuq825@gmail.com> --- drivers/dma-buf/dma-resv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/dma-buf/dma-resv.c b/drivers/dma-buf/dma-resv.c index 42a8f3f11681..709002515550 100644 --- a/drivers/dma-buf/dma-resv.c +++ b/drivers/dma-buf/dma-resv.c @@ -471,7 +471,7 @@ int dma_resv_get_fences_rcu(struct dma_resv *obj, if (pfence_excl) *pfence_excl = fence_excl; else if (fence_excl) - shared[++shared_count] = fence_excl; + shared[shared_count++] = fence_excl; if (!shared_count) { kfree(shared); -- 2.17.1 _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-09-22 7:49 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-09-22 7:49 Qiang Yu [this message] 2019-09-22 7:49 ` [PATCH] dma-buf/resv: fix exclusive fence get Qiang Yu 2019-09-22 12:17 ` Chris Wilson 2019-09-22 12:17 ` Chris Wilson 2019-09-22 12:50 ` Chris Wilson 2019-09-22 12:50 ` Chris Wilson 2019-10-10 14:27 ` Qiang Yu 2019-10-10 14:27 ` Qiang Yu 2019-10-10 14:33 ` Koenig, Christian 2019-10-10 14:33 ` Koenig, Christian 2019-09-30 7:22 ` Daniel Vetter 2019-09-30 7:22 ` Daniel Vetter 2019-09-30 8:57 ` Koenig, Christian 2019-09-30 8:57 ` Koenig, Christian 2019-10-08 16:43 ` Daniel Vetter 2019-10-08 16:43 ` Daniel Vetter
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=20190922074900.853-1-yuq825@gmail.com \ --to=yuq825@gmail.com \ --cc=christian.koenig@amd.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=lima@lists.freedesktop.org \ --cc=linaro-mm-sig@lists.linaro.org \ --cc=linux-media@vger.kernel.org \ --cc=sumit.semwal@linaro.org \ /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: linkBe 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.