public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tursulin@igalia.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Tvrtko Ursulin" <tursulin@ursulin.net>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Oded Gabbay" <ogabbay@kernel.org>,
	"Lucas De Marchi" <lucas.demarchi@intel.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: [PULL] drm-intel-fixes
Date: Thu, 12 Sep 2024 08:07:55 +0100	[thread overview]
Message-ID: <ZuKTN2XngNhBB3z3@linux> (raw)


Hi Dave, Sima,

It is late in the cycle and luckily the fix in this weeks PR is just
something to satisfy static analyzers, nothing that can happen in reality,
so pulling it is even optional.

Regards,

Tvrtko

drm-intel-fixes-2024-09-12:
- Prevent a possible int overflow in wq offsets [guc] (Nikita Zhandarovich)
The following changes since commit da3ea35007d0af457a0afc87e84fddaebc4e0b63:

  Linux 6.11-rc7 (2024-09-08 14:50:28 -0700)

are available in the Git repository at:

  https://gitlab.freedesktop.org/drm/i915/kernel.git tags/drm-intel-fixes-2024-09-12

for you to fetch changes up to d3d37f74683e2f16f2635ee265884f7ca69350ae:

  drm/i915/guc: prevent a possible int overflow in wq offsets (2024-09-10 08:13:51 +0100)

----------------------------------------------------------------
- Prevent a possible int overflow in wq offsets [guc] (Nikita Zhandarovich)

----------------------------------------------------------------
Nikita Zhandarovich (1):
      drm/i915/guc: prevent a possible int overflow in wq offsets

 drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

             reply	other threads:[~2024-09-12  7:08 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12  7:07 Tvrtko Ursulin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-09 10:07 [PULL] drm-intel-fixes Joonas Lahtinen
2026-04-09 10:24 ` Joonas Lahtinen
2026-04-02 10:21 Joonas Lahtinen
2026-03-26  7:17 Joonas Lahtinen
2026-03-19  7:17 Joonas Lahtinen
2026-03-12  8:54 Tvrtko Ursulin
2026-03-05  7:42 Joonas Lahtinen
2026-02-25 14:40 Joonas Lahtinen
2026-01-15 10:01 Jani Nikula
2025-12-31 17:51 Jani Nikula
2025-11-26 15:44 Rodrigo Vivi
2025-11-20 14:17 Rodrigo Vivi
2025-11-13 13:29 Rodrigo Vivi
2025-11-06 14:31 Rodrigo Vivi
2025-10-30 13:51 Rodrigo Vivi
2025-10-31 18:09 ` Simona Vetter
2025-10-23 12:45 Rodrigo Vivi
2025-10-24 11:39 ` Simona Vetter
2025-10-16 12:43 Rodrigo Vivi
2025-09-25  7:38 Tvrtko Ursulin
2025-09-17 15:12 Tvrtko Ursulin
2025-09-10 10:36 Tvrtko Ursulin
2025-08-20 11:48 Tvrtko Ursulin
2025-08-13 21:43 Tvrtko Ursulin
2025-08-14 16:47 ` Imre Deak
2025-07-24 14:36 Rodrigo Vivi
2025-07-17 15:02 Rodrigo Vivi
2025-07-17 18:25 ` Rodrigo Vivi
2025-07-10 22:32 Rodrigo Vivi
2025-07-11  9:35 ` Simona Vetter
2025-07-03  5:29 Joonas Lahtinen
2025-06-26  6:43 Joonas Lahtinen
2025-06-18  6:42 Joonas Lahtinen
2025-05-09  7:30 Jani Nikula
2025-04-30  9:22 Jani Nikula
2025-04-17  7:04 Jani Nikula
2025-04-09 12:41 Jani Nikula
2025-03-13 16:25 Rodrigo Vivi
2025-03-06 17:52 Rodrigo Vivi
2025-02-27 16:22 Rodrigo Vivi
2025-02-20 17:03 Rodrigo Vivi
2025-02-13 17:23 Rodrigo Vivi
2025-02-06 14:11 Rodrigo Vivi
2025-02-06 14:13 ` Rodrigo Vivi
2025-01-15 16:06 Tvrtko Ursulin
2025-01-08 18:18 Tvrtko Ursulin
2024-12-25 13:37 Tvrtko Ursulin
2024-12-18 15:26 Tvrtko Ursulin
2024-12-11 18:04 Tvrtko Ursulin
2024-11-14  7:20 Joonas Lahtinen
2024-10-24  5:59 Joonas Lahtinen
2024-10-17  8:31 Joonas Lahtinen
2024-10-10  7:02 Joonas Lahtinen
2024-10-02 15:25 Joonas Lahtinen
2024-09-05  8:16 Tvrtko Ursulin
2024-08-29  7:06 Joonas Lahtinen
2024-08-22  5:40 Joonas Lahtinen
2024-08-08  8:45 Tvrtko Ursulin
     [not found] ` <8f7c531a-ecb9-4c30-b4bb-2bdf3056ff34@kernel.org>
     [not found]   ` <3b87c155-f35d-4812-a4b3-ac5e0bfe0c18@kernel.org>
2024-08-09  7:13     ` Dave Airlie
2024-08-09  8:35     ` Joonas Lahtinen
2024-08-01  6:02 Joonas Lahtinen
2024-07-02  8:28 Jani Nikula
2024-07-04 14:14 ` Daniel Vetter
2024-06-27  8:14 Jani Nikula
2024-06-19 10:45 Jani Nikula
2024-05-30  7:30 Jani Nikula
2024-05-08 19:32 Rodrigo Vivi
2024-04-10 21:51 Rodrigo Vivi
2024-04-04 17:45 Rodrigo Vivi
2024-03-29  1:32 Rodrigo Vivi
2024-03-29 10:23 ` Musial, Ewelina
2024-03-29 13:25   ` Rodrigo Vivi
2024-03-07  8:19 Joonas Lahtinen
2024-03-01  8:14 Joonas Lahtinen

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=ZuKTN2XngNhBB3z3@linux \
    --to=tursulin@igalia.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=ogabbay@kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tursulin@ursulin.net \
    --cc=tzimmermann@suse.de \
    /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