public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: "Intel graphics driver community testing & development"
	<intel-gfx@lists.freedesktop.org>,
	Direct Rendering Infrastructure - Development
	<dri-devel@lists.freedesktop.org>,
	Ville Syrjälä <ville.syrjala@linux.intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>
Subject: Re: [PATCH] Revert "i915: don't use a vma that didn't match the context VM"
Date: Tue, 12 May 2026 08:15:56 -0700	[thread overview]
Message-ID: <CAHk-=wjKXGC=rK_pbRY9o2dkAumRakPGws0o2nfZgqbLS0vG6w@mail.gmail.com> (raw)
In-Reply-To: <20260512085848.208008-1-joonas.lahtinen@linux.intel.com>

On Tue, 12 May 2026 at 01:59, Joonas Lahtinen
<joonas.lahtinen@linux.intel.com> wrote:
>
> Commit is no-op as per discussion in the linked mail thread.
> The debated UAF scenario has not been possible in mainline kernel
> since 2021.

That was never the issue.

The issue was that the code used to do this:

                if (likely(vma && vma->vm == vm))
                        vma = i915_vma_tryget(vma);

and the vma->vm == vm condition was nonsensical - and if it ever was
false, that code was all horribly buggy.

So the "since 2021" is complete nonsense.

It's only since April this year - commit a13edf9b92fc ("drm/i915/gem:
Drop check for changed VM in EXECBUF") that the "else" side is now
pointless and the revert makes sense.

Stop writing misleading commit logs and excuses for bad code. There is
no "since 2021".

                Linus

  reply	other threads:[~2026-05-12 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  8:58 [PATCH] Revert "i915: don't use a vma that didn't match the context VM" Joonas Lahtinen
2026-05-12 15:15 ` Linus Torvalds [this message]
2026-05-16  3:59 ` Claude review: " Claude Code Review Bot
2026-05-16  3:59 ` Claude Code Review Bot

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='CAHk-=wjKXGC=rK_pbRY9o2dkAumRakPGws0o2nfZgqbLS0vG6w@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=tursulin@ursulin.net \
    --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