From: Greg KH <gregkh@linuxfoundation.org>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Yassine Mounir <sosohero200@gmail.com>,
intel-gfx@lists.freedesktop.org, security@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: AI slop security report against i915 (Was: Re: [PATCH v2] drm/i915/gem: Fix UAF race in eb_relocate_vma)
Date: Thu, 26 Mar 2026 09:45:51 +0100 [thread overview]
Message-ID: <2026032643-disband-reorder-c0fd@gregkh> (raw)
In-Reply-To: <177450809396.10669.10897074578574249353@jlahtine-mobl>
On Thu, Mar 26, 2026 at 08:54:53AM +0200, Joonas Lahtinen wrote:
> (+ Adding back security mailing list (where this started) and LKML for them
> to be aware of any further bogus security reports from the author)
Ugh, I was kind of thinking this might be the case based on the original
interactions here, but was willing to give the benifit of the doubt.
Time to go reset the "Days since we recieved AI slop reports" counter
back to 0...
thanks for following through on this.
greg k-h
next prev parent reply other threads:[~2026-03-26 8:46 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
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 [this message]
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=2026032643-disband-reorder-c0fd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=security@kernel.org \
--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