From: "Christian König" <christian.koenig@amd.com>
To: Baineng Shou <shoubaineng@gmail.com>, sumit.semwal@linaro.org
Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
phasta@kernel.org, tursulin@ursulin.net, akash.goel@arm.com
Subject: Re: [PATCH] dma-buf/test: add KUnit case for dma_fence_dedup_array() empty input
Date: Tue, 30 Jun 2026 10:29:05 +0200 [thread overview]
Message-ID: <0a02f85f-088c-4479-9e58-3b564931bfd6@amd.com> (raw)
In-Reply-To: <20260630060436.1527498-1-shoubaineng@gmail.com>
On 6/30/26 08:04, Baineng Shou wrote:
> Add a KUnit case verifying that dma_fence_dedup_array() returns 0,
> not 1, when called with num_fences == 0. This locks down the
> contract documented in the kernel-doc and prevents a regression
> of commit 77a9298741f8 ("dma-fence: Make dma_fence_dedup_array()
> robust against 0-count input").
>
> Suggested-by: Christian König <christian.koenig@amd.com>
> Signed-off-by: Baineng Shou <shoubaineng@gmail.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Going to push this to drm-misc-next later today. I also pinged our intern to write a cleanup patch whic consistently use size_t for the number of array elements in the code.
Thanks,
Christian.
> ---
> drivers/dma-buf/st-dma-fence-unwrap.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/dma-buf/st-dma-fence-unwrap.c b/drivers/dma-buf/st-dma-fence-unwrap.c
> index 4e7ee25372ba..72dea6091d58 100644
> --- a/drivers/dma-buf/st-dma-fence-unwrap.c
> +++ b/drivers/dma-buf/st-dma-fence-unwrap.c
> @@ -370,6 +370,15 @@ static void test_unwrap_merge_seqno(struct kunit *test)
> dma_fence_put(f1);
> }
>
> +static void test_dedup_empty(struct kunit *test)
> +{
> + struct dma_fence *fence[1] = { NULL };
> + int ret;
> +
> + ret = dma_fence_dedup_array(fence, 0);
> + KUNIT_EXPECT_EQ(test, ret, 0);
> +}
> +
> static void test_unwrap_merge_order(struct kunit *test)
> {
> struct dma_fence *fence, *f1, *f2, *a1, *a2, *c1, *c2;
> @@ -595,6 +604,7 @@ static struct kunit_case dma_fence_unwrap_cases[] = {
> KUNIT_CASE(test_unwrap_merge_order),
> KUNIT_CASE(test_unwrap_merge_complex),
> KUNIT_CASE(test_unwrap_merge_complex_seqno),
> + KUNIT_CASE(test_dedup_empty),
> {}
> };
>
prev parent reply other threads:[~2026-06-30 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 6:04 [PATCH] dma-buf/test: add KUnit case for dma_fence_dedup_array() empty input Baineng Shou
2026-06-30 8:29 ` Christian König [this message]
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=0a02f85f-088c-4479-9e58-3b564931bfd6@amd.com \
--to=christian.koenig@amd.com \
--cc=akash.goel@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=phasta@kernel.org \
--cc=shoubaineng@gmail.com \
--cc=sumit.semwal@linaro.org \
--cc=tursulin@ursulin.net \
/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