From: Genes Lists <lists@sapience.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, lucas.demarchi@intel.com,
thomas.hellstrom@linux.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: Mon, 30 Dec 2024 15:52:14 -0500 [thread overview]
Message-ID: <5f756542aaaf241d512458f306707bda3b249671.camel@sapience.com> (raw)
In-Reply-To: <20241230145002.3cc11717@gandalf.local.home>
[-- Attachment #1.1: Type: text/plain, Size: 478 bytes --]
On Mon, 2024-12-30 at 14:50 -0500, Steven Rostedt wrote:
> On Mon, 30 Dec 2024 14:13:29 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > I guess the "fix" would be to have the check code ignore pointer to
> > arrays, assuming they are "ok".
>
> Can you try this patch?
>
> -- Steve
Confirmed - all quiet now with 6.12.7 + your patch - I can test
mainline too but doesn't look that useful.
Thank you for sorting this out so quickly.
--
Gene
[-- Attachment #1.2: Type: text/html, Size: 1308 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-01-02 18:12 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 [this message]
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
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=5f756542aaaf241d512458f306707bda3b249671.camel@sapience.com \
--to=lists@sapience.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=regressions@lists.linux.dev \
--cc=rostedt@goodmis.org \
--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