From: Julian Braha <julianbraha@gmail.com>
To: Michael Bommarito <michael.bommarito@gmail.com>,
Melissa Wen <mwen@igalia.com>, Maira Canal <mcanal@igalia.com>
Cc: Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Iago Toral Quiroga <itoral@igalia.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] drm/v3d: add KUnit reproducer for the copy-query out-of-bounds write
Date: Mon, 15 Jun 2026 15:12:31 +0100 [thread overview]
Message-ID: <9a446f01-3608-47c0-b53c-323c15749705@gmail.com> (raw)
In-Reply-To: <20260614131100.2525157-3-michael.bommarito@gmail.com>
Hi Michael,
On 6/14/26 14:11, Michael Bommarito wrote:
> +config DRM_V3D_COPY_QUERY_KUNIT_TEST
> + bool "KUnit test for V3D CPU-job copy-query bounds"
> + depends on DRM_V3D && KUNIT=y
> + select DRM_KUNIT_TEST_HELPERS
> + help
> + Builds a KUnit suite that drives the V3D CPU-job copy-timestamp-query
> + handler over a real shmem-backed BO to exercise the destination-buffer
> + bounds. Used to reproduce the copy-query out-of-bounds write under
> + KASAN. If in doubt, say N.
Could you hide this option from the Kconfig frontend
when KUNIT_ALL_TESTS is enabled?
E.g.:
bool "KUnit test for V3D CPU-job copy-query bounds" if !KUNIT_ALL_TESTS
From Documentation/dev-tools/kunit/style.rst:
"This Kconfig entry must:
<snip>
* be visible only if ``CONFIG_KUNIT_ALL_TESTS`` is not enabled."
- Julian Braha
prev parent reply other threads:[~2026-06-15 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 13:10 [PATCH 0/2] drm/v3d: bound CPU-job copy-query writes to the destination BO Michael Bommarito
2026-06-14 13:10 ` [PATCH 1/2] drm/v3d: validate copy-query buffer bounds against destination BO size Michael Bommarito
2026-06-14 20:12 ` Maíra Canal
2026-06-14 21:12 ` Michael Bommarito
2026-06-14 13:11 ` [PATCH 2/2] drm/v3d: add KUnit reproducer for the copy-query out-of-bounds write Michael Bommarito
2026-06-15 14:12 ` Julian Braha [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=9a446f01-3608-47c0-b53c-323c15749705@gmail.com \
--to=julianbraha@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=itoral@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcanal@igalia.com \
--cc=michael.bommarito@gmail.com \
--cc=mripard@kernel.org \
--cc=mwen@igalia.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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
Powered by JetHome