From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Yassine Mounir <sosohero200@gmail.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
<gregkh@linuxfoundation.org>, <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2] drm/i915/gem: Fix UAF race in eb_relocate_vma
Date: Wed, 25 Mar 2026 18:14:23 -0400 [thread overview]
Message-ID: <acReP5LYxOKCG80B@intel.com> (raw)
In-Reply-To: <CANq=4mC3+B4akvpp=nr_w1bbnhDwUXx=EzyQtHQpR9DN=ewCMA@mail.gmail.com>
On Wed, Mar 25, 2026 at 01:30:52PM -0400, Yassine Mounir wrote:
> "Hi Rodrigo, I've submitted the issue and the V2 patch under #15882. I've
> marked it as confidential as it addresses a potential UAF security risk.
> Looking forward to your review."
Could you please share a URL for that. I could not find it.
> On Wed, 25 Mar 2026 at 13:30, Yassine Mounir <[1]sosohero200@gmail.com>
> wrote:
>
> >> "Hi Rodrigo,
>
> >> I am currently following your instructions to file the bug report on
> >> GitLab. However, my new GitLab account is pending manual approval due
> >> to the current spam restrictions on [2]freedesktop.org. I have
> >> contacted the admins for full permissions.
>
> >> In the meantime, I have prepared all the logs (KASAN splat from vanilla
> >> drm-tip and the clean dmesg from the patched version). As soon as the
> >> account is active, I will post the link here.
>
> >> Thank you for your patience."
>
> > On Wed, 25 Mar 2026 at 11:47, Rodrigo Vivi <[3]rodrigo.vivi@intel.com>
> > wrote:
>
> >> On Wed, Mar 25, 2026 at 04:07:17PM +0200, Joonas Lahtinen wrote:
> >> > Quoting Yassine Mounir (2026-03-25 10:20:58)
> >> > > Hi Joonas,
> >> > > Thank you for the detailed feedback. I apologize for the double tag
> >> and the
> >> > > direct submission to Greg; I'm still refining my workflow.
> >> >
> >> > Ok, then to level set some expectations:
> >> >
> >> > Have you actually confirmed that the code you have submitted compiles
> >> > and does fix the bug you reported?
> >> >
> >> > Expectation is that you run the reproducer on top of drm-tip and see
> >> a
> >> > crash where you pick the dmesg/KASAN splat from, then you run drm-tip
> >> > with the patch you have prepared and there is no crash.
>
> >> Exactly.
>
> >> Before any further submission, please let's get back to square 0 here.
>
> >> 0. Please file a bug to our gilab/issues:
> >> [4]https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html
>
> >> Do that against the drm-tip branch and provide all the log information
> >> from your experiments.
>
> >> 1. If you have a proposed patch, also please confirm that it actually
> >> fix
> >> the issues that you are solving.
>
> >> 2. Whenever using AI to help you with the code please ensure you comply
> >> with this:
>
> >> Documentation/process/generated-content.rst
>
> >> Thanks,
> >> Rodrigo.
>
> >> >
> >> > Regards, Joonas
>
> References
>
> Visible links
> 1. mailto:sosohero200@gmail.com
> 2. http://freedesktop.org/
> 3. mailto:rodrigo.vivi@intel.com
> 4. https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html
next prev parent reply other threads:[~2026-03-25 22:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 15:17 [PATCH v2] [PATCH v2] drm/i915/gem: Fix UAF race in eb_relocate_vma Yassine Mounir
2026-03-25 8:01 ` Joonas Lahtinen
2026-03-25 8:20 ` Yassine Mounir
2026-03-25 14:07 ` Joonas Lahtinen
2026-03-25 15:43 ` Yassine Mounir
2026-03-25 15:46 ` Rodrigo Vivi
2026-03-25 17:30 ` Yassine Mounir
2026-03-25 17:30 ` Yassine Mounir
2026-03-25 22:14 ` Rodrigo Vivi [this message]
2026-03-25 22:37 ` Yassine Mounir
2026-03-26 6:54 ` AI slop security report against i915 (Was: Re: [PATCH v2] drm/i915/gem: Fix UAF race in eb_relocate_vma) Joonas Lahtinen
2026-03-26 8:45 ` Greg KH
2026-03-25 15:34 ` ✗ LGCI.VerificationFailed: failure for drm/i915/gem: Fix UAF race in eb_relocate_vma Patchwork
2026-03-26 12:32 ` [PATCH v2] [PATCH v2] " Ville Syrjälä
2026-03-26 15:19 ` Linus Torvalds
2026-04-03 22:12 ` Linus Torvalds
2026-04-03 22:35 ` Yassine Mounir
2026-04-03 22:38 ` Yassine Mounir
2026-04-07 16:38 ` Joonas Lahtinen
2026-04-07 16:46 ` Linus Torvalds
2026-04-08 11:15 ` Joonas Lahtinen
2026-04-08 15:38 ` Linus Torvalds
2026-04-08 16:24 ` Joonas Lahtinen
2026-04-09 15:45 ` Linus Torvalds
2026-04-13 4:39 ` Joonas Lahtinen
2026-04-09 8:05 ` Matthew Brost
2026-04-09 15:50 ` Linus Torvalds
2026-04-07 16:58 ` Simona Vetter
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=acReP5LYxOKCG80B@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=sosohero200@gmail.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