public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tursulin@ursulin.net>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Intel graphics driver community testing & development
	<intel-gfx@lists.freedesktop.org>
Cc: "Direct Rendering Infrastructure - Development"
	<dri-devel@lists.freedesktop.org>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Linus Torvalds" <torvalds@linuxfoundation.org>,
	"Simona Vetter" <simona.vetter@ffwll.ch>,
	"Andi Shyti" <andi.shyti@kernel.org>
Subject: Re: [PATCH v4] drm/i915/gem: Drop check for changed VM in EXECBUF
Date: Thu, 9 Apr 2026 10:11:41 +0100	[thread overview]
Message-ID: <b8d02a4c-e20d-4814-8ba3-eaba6b701b6f@ursulin.net> (raw)
In-Reply-To: <20260409053111.8914-1-joonas.lahtinen@linux.intel.com>


On 09/04/2026 06:31, Joonas Lahtinen wrote:
> Since the introduction of d4433c7600f7 ("drm/i915/gem: Use the proto-context
> to handle create parameters (v5)") it has not been possible for VM to change
> after context creation so the check will never fail.
> 
> Sima's analysis:
> 
>    This check was added in f7ce8639f6ff ("drm/i915/gem: Split the context's
>    obj:vma lut into its own mutex") but without any hint in the commit
>    message as to why. In another hunk of that commit there's a hint though in
>    __eb_add_lut:
> 
>            /* user racing with ctx set-vm */
> 
>    This would mean that this bug was introduced in e0695db7298e ("drm/i915:
>    Create/destroy VM (ppGTT) for use with contexts"), which allowed to change
>    the gem_ctx->vm at runtime, opening up the race that was partially fixed
>    in the earlier referenced commit about a year later.
> 
>    But it cannot be exploited anymore in anything remotely recent because
>    with the introduction of proto-contexts we've made gem_ctx->vm invariant
>    again, exactly to preemptively close all these potential issues.
>    Specifically d4433c7600f7 ("drm/i915/gem: Use the proto-context to handle
>    create parameters (v5)") is the vm specific part of the proto-context
>    work.
> 
> v3:
> - Include Sima's analysis and WARN_ON_ONCE
> 
> v4:
> - Focus only on latest mainline codebase
> 
> References: https://lore.kernel.org/all/20260324151741.29338-1-sosohero200@gmail.com/
> Reported-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Linus Torvalds <torvalds@linuxfoundation.org>
> Cc: Simona Vetter <simona.vetter@ffwll.ch>
> Cc: Tvrtko Ursulin <tursulin@ursulin.net>
> Cc: Andi Shyti <andi.shyti@kernel.org>
> Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> ---
>   drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> index bd608cea396f..621f07a55c38 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> @@ -895,7 +895,7 @@ static struct i915_vma *eb_lookup_vma(struct i915_execbuffer *eb, u32 handle)
>   
>   		rcu_read_lock();
>   		vma = radix_tree_lookup(&eb->gem_context->handles_vma, handle);
> -		if (likely(vma && vma->vm == vm))
> +		if (likely(vma))
>   			vma = i915_vma_tryget(vma);
>   		rcu_read_unlock();
>   		if (likely(vma))

Analysis reads correct to me.

Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>

Regards,

Tvrtko


  parent reply	other threads:[~2026-04-09  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09  5:31 [PATCH v4] drm/i915/gem: Drop check for changed VM in EXECBUF Joonas Lahtinen
2026-04-09  6:24 ` ✓ i915.CI.BAT: success for " Patchwork
2026-04-09  9:11 ` Tvrtko Ursulin [this message]
2026-04-09 17:27 ` ✓ i915.CI.Full: " 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=b8d02a4c-e20d-4814-8ba3-eaba6b701b6f@ursulin.net \
    --to=tursulin@ursulin.net \
    --cc=andi.shyti@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=simona.vetter@ffwll.ch \
    --cc=torvalds@linuxfoundation.org \
    --cc=ville.syrjala@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