All of lore.kernel.org
 help / color / mirror / Atom feed
From: <linux-kernel@dittrich.top>
To: <intel-gfx@lists.freedesktop.org>
Cc: <krzysztof.karas@intel.com>
Subject: Re: [PATCH] drm/i915/gem: Prevent overstepping exec array boundary
Date: Sun, 4 Oct 2026 16:09:35 +0200	[thread overview]
Message-ID: <034701dd5409$fca1e490$f5e5adb0$@dittrich.top> (raw)
In-Reply-To: <20260911061145.3535489-1-krzysztof.karas@intel.com>

Hi,

I observed repeated kfree() Oopses in eb_relocate_parse_slow() during VAAPI
video processing on real Haswell hardware (8086:0412) on Debian
6.12.107+deb13-amd64.

After applying 2a0158925fb9 ("drm/i915/gem: Prevent overstepping exec array
boundary") and verifying the loaded module, VAAPI decode/scale/H.264 encode
and full video analyses completed. The previous Oops did not recur and no
new
kernel/GPU error was detected in these runs.

Please carry this already accepted fix into mainline and the affected
stable/LTS branches, particularly 6.12. I see it already has
Cc: stable #5.10+.

AI assistance was used for log/source analysis, test automation and
drafting; the reported tests ran on actual hardware.

Thanks.


      parent reply	other threads:[~2026-10-05 23:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11  6:11 [PATCH] drm/i915/gem: Prevent overstepping exec array boundary Krzysztof Karas
2026-09-11  6:29 ` sashiko-bot
2026-09-11  7:04 ` ✓ i915.CI.BAT: success for " Patchwork
2026-09-12  3:05 ` ✗ i915.CI.Full: failure " Patchwork
2026-09-30  0:54 ` [PATCH] " Andi Shyti
2026-09-30  5:57   ` Krzysztof Karas
2026-10-04 14:09 ` linux-kernel [this message]

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='034701dd5409$fca1e490$f5e5adb0$@dittrich.top' \
    --to=linux-kernel@dittrich.top \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=krzysztof.karas@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.