[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250101204959.6e297af6@batman.local.home>
Date: Wed, 1 Jan 2025 20:49:59 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Thomas Hellström <thomas.hellstrom@...ux.intel.com>
Cc: Genes Lists <lists@...ience.com>, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org, intel-xe@...ts.freedesktop.org,
lucas.demarchi@...el.com, stable@...r.kernel.org,
regressions@...ts.linux.dev, Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [REGRESSION][BISECTED] Re: 6.12.7 stable new error: event
xe_bo_move has unsafe dereference of argument 4
On Wed, 01 Jan 2025 21:55:26 +0100
Thomas Hellström <thomas.hellstrom@...ux.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
Powered by blists - more mailing lists