Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Maxime Ripard <mripard@kernel.org>
Subject: Re: [Intel-xe] [PATCH v3 0/2] drm/tests: Fix for UAF and a test for drm_exec lock alloc tracking warning
Date: Thu, 7 Sep 2023 16:37:53 +0200	[thread overview]
Message-ID: <b3ab850d-9da2-0b19-2aa1-fa5a2c3dc079@amd.com> (raw)
In-Reply-To: <20230907135339.7971-1-thomas.hellstrom@linux.intel.com>

Am 07.09.23 um 15:53 schrieb Thomas Hellström:
> While trying to replicate a weird drm_exec lock alloc tracking warning
> using the drm_exec kunit test, the warning was shadowed by a UAF warning
> from KASAN due to a bug in the drm kunit helpers.
>
> Patch 1 fixes that drm kunit UAF.
> Patch 2 introduces a drm_exec kunit subtest that fails if the conditions
>        for the weird warning are met.
>
> The series previously also had a patch with a drm_exec workaround for the
> warning but that patch has already been commited to drm_misc_next_fixes.

Thinking more about this what happens when somebody calls 
drm_exec_unlock_obj() on the first locked object?

Christian.

>
> v2:
> - Rewording of commit messages
> - Add some commit message tags
> v3:
> - Remove an already committed patch
> - Rework the test to not require dmesg inspection (Maxime Ripard)
> - Condition the test on CONFIG_LOCK_ALLOC
> - Update code comments and commit messages (Maxime Ripard)
>
> Cc: Maxime Ripard <mripard@kernel.org>
> Cc: Christian König <christian.koenig@amd.com>
>
> Thomas Hellström (2):
>    drm/tests: helpers: Avoid a driver uaf
>    drm/tests/drm_exec: Add a test for object freeing within
>      drm_exec_fini()
>
>   drivers/gpu/drm/tests/drm_exec_test.c | 82 +++++++++++++++++++++++++++
>   include/drm/drm_kunit_helpers.h       |  4 +-
>   2 files changed, 85 insertions(+), 1 deletion(-)
>


  parent reply	other threads:[~2023-09-07 14:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 13:53 [Intel-xe] [PATCH v3 0/2] drm/tests: Fix for UAF and a test for drm_exec lock alloc tracking warning Thomas Hellström
2023-09-07 13:53 ` [Intel-xe] [PATCH v3 1/2] drm/tests: helpers: Avoid a driver uaf Thomas Hellström
2023-09-07 14:50   ` Maxime Ripard
2023-09-11 12:40   ` Francois Dugast
2023-09-11 13:04     ` Thomas Hellström
2023-09-14 11:59   ` [Intel-xe] (subset) " Maxime Ripard
2023-09-07 13:53 ` [Intel-xe] [PATCH v3 2/2] drm/tests/drm_exec: Add a test for object freeing within drm_exec_fini() Thomas Hellström
2023-09-07 14:52   ` Maxime Ripard
2023-09-07 14:37 ` Christian König [this message]
2023-09-07 14:47   ` [Intel-xe] [PATCH v3 0/2] drm/tests: Fix for UAF and a test for drm_exec lock alloc tracking warning Thomas Hellström
2023-09-07 14:49     ` Christian König
2023-09-08  7:37       ` Thomas Hellström
2023-09-08  8:52         ` Christian König
2023-09-08  9:04           ` Thomas Hellström
2023-09-08  9:14             ` Christian König
2023-09-08 11:13               ` Thomas Hellström
2023-09-08 14:31                 ` Thomas Hellström
2023-09-07 23:49 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-09-07 23:49 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-07 23:50 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-07 23:57 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-07 23:57 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-07 23:59 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-08  0:30 ` [Intel-xe] ✓ CI.BAT: " Patchwork

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=b3ab850d-9da2-0b19-2aa1-fa5a2c3dc079@amd.com \
    --to=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=mripard@kernel.org \
    --cc=thomas.hellstrom@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox