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
