From: Steven Rostedt <rostedt@goodmis.org>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: Genes Lists <lists@sapience.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, lucas.demarchi@intel.com,
stable@vger.kernel.org, regressions@lists.linux.dev,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [REGRESSION][BISECTED] Re: 6.12.7 stable new error: event xe_bo_move has unsafe dereference of argument 4
Date: Wed, 1 Jan 2025 20:49:59 -0500 [thread overview]
Message-ID: <20250101204959.6e297af6@batman.local.home> (raw)
In-Reply-To: <5ca1c5b64c313108ea2aa005ae273f1ba8051e7f.camel@linux.intel.com>
On Wed, 01 Jan 2025 21:55:26 +0100
Thomas Hellström <thomas.hellstrom@linux.intel.com> wrote:
> FWIW, we actually worked around this during the holiday in the drm-xe-
> next branch in the xe driver since it was breaking our CI. Was planning
> to include it for drm-xe-fixes for tomorrow. Since xe appeared to be
> the only driver hitting this, our assumption was that it'd be better
> fixed in the driver.
The driver wasn't broken. I changed the verifier and it incorrectly
flagged that driver's trace event as unsafe. Yeah, it's the only driver
to use an array of strings, but it doesn't mean it was wrong.
-- Steve
next prev parent reply other threads:[~2025-01-02 1:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 16:15 6.12.7 stable new error: event xe_bo_move has unsafe dereference of argument 4 Genes Lists
2024-12-30 18:55 ` [REGRESSION][BISECTED] " Genes Lists
2024-12-30 19:13 ` Steven Rostedt
2024-12-30 19:50 ` Steven Rostedt
2024-12-30 20:20 ` Genes Lists
2024-12-30 20:52 ` Genes Lists
2024-12-30 21:03 ` Steven Rostedt
2024-12-30 21:07 ` Genes Lists
2025-01-01 20:55 ` Thomas Hellström
2025-01-02 1:49 ` Steven Rostedt [this message]
2025-01-04 17:41 ` Andrea Amorosi
2025-01-04 17:43 ` Andrea Amorosi
2025-01-04 20:09 ` Genes Lists
2025-01-06 19:41 ` Steven Rostedt
2024-12-30 20:23 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-30 20:23 ` ✗ CI.checkpatch: warning " Patchwork
2024-12-30 20:24 ` ✓ CI.KUnit: success " Patchwork
2024-12-30 20:42 ` ✓ CI.Build: " Patchwork
2024-12-30 20:45 ` ✓ CI.Hooks: " Patchwork
2024-12-30 20:46 ` ✓ CI.checksparse: " Patchwork
2024-12-30 21:28 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-31 0:47 ` ✗ Xe.CI.Full: failure " 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=20250101204959.6e297af6@batman.local.home \
--to=rostedt@goodmis.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@sapience.com \
--cc=lucas.demarchi@intel.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=torvalds@linux-foundation.org \
/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