From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: David Francis <David.Francis@amd.com>, <igt-dev@lists.freedesktop.org>
Cc: <tvrtko.ursulin@igalia.com>,
Vitaly Prosyak <vitaly.prosyak@amd.com>,
Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Christian Konig <christian.koenig@amd.com>,
Simona Vetter <simona@ffwll.ch>,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH] tests/intel: Add edge case and race condition tests for GEM_CHANGE_HANDLE
Date: Tue, 3 Nov 2026 11:56:01 +0100 [thread overview]
Message-ID: <DMLIRWF18QTP.NGNWV1AUHAMJ@intel.com> (raw)
In-Reply-To: <20261007141209.2928162-1-David.Francis@amd.com>
Hi David,
On Wed Oct 7, 2026 at 4:12 PM CEST, David Francis wrote:
> From: Vitaly Prosyak <vitaly.prosyak@amd.com>
>
> Add a GPU-agnostic GEM_CHANGE_HANDLE tests. These test for basic
> functionality, edge cases, and race conditions of this ioctl against
> itself, gem close, gem create, and prime import and export.
>
> GEM_CHANGE_HANDLE is currently wired to drm_invalid_op in DRM core. This IGT
> coverage is a prerequisite for validating the eventual kernel-side ioctl
> implementation and makes fixing its security bugs safer.
>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Cc: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
> Cc: Christian Konig <christian.koenig@amd.com>
> Cc: Simona Vetter <simona@ffwll.ch>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> Signed-off-by: Vitaly Prosyak <vitaly.prosyak@amd.com>
> Signed-off-by: David Francis <David.Francis@amd.com>
> ---
To me these tests look reasonable, but we need to make sure we don't
pollute CI with failures. GEM_CHANGE_HANDLE is still drm_invalid_op
in DRM core, so on current kernels every subtest fails.
The best path would be to merge the kernel side first. But since these
tests are a prerequisite for the kernel patches, we need to work around
that somehow. Until the kernel part lands, the tests could skip when the
ioctl returns -EINVAL or -ENOTTY. Could you add that in the next revision?
For the contribution process, please take a look at the guide:
https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/blob/master/CONTRIBUTING.md
In short, patches are reviewed on the igt-dev mailing list, not through
GitLab merge requests. It would be nice to get an ack from one of the
maintainers (Kamil is Cc'd) before this is merged.
--
Best regards,
Sebastian
next prev parent reply other threads:[~2026-11-03 10:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 14:12 [PATCH] tests/intel: Add edge case and race condition tests for GEM_CHANGE_HANDLE David Francis
2026-10-07 14:13 ` Francis, David
2026-10-07 17:05 ` Francis, David
2026-10-07 15:49 ` ✗ Fi.CI.BUILD: failure for tests/intel: Add edge case and race condition tests for GEM_CHANGE_HANDLE (rev2) Patchwork
2026-10-07 18:17 ` ✗ Fi.CI.BUILD: failure for tests/intel: Add edge case and race condition tests for GEM_CHANGE_HANDLE (rev3) Patchwork
2026-10-14 9:42 ` [PATCH] tests/intel: Add edge case and race condition tests for GEM_CHANGE_HANDLE Sebastian Brzezinka
2026-10-14 13:25 ` Francis, David
2026-10-15 15:44 ` Kamil Konieczny
2026-11-03 10:56 ` Sebastian Brzezinka [this message]
2026-11-05 10:49 ` Tvrtko Ursulin
2026-11-05 10:56 ` Sebastian Brzezinka
2026-11-05 11:07 ` Tvrtko Ursulin
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=DMLIRWF18QTP.NGNWV1AUHAMJ@intel.com \
--to=sebastian.brzezinka@intel.com \
--cc=David.Francis@amd.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=simona@ffwll.ch \
--cc=tvrtko.ursulin@igalia.com \
--cc=vitaly.prosyak@amd.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.