Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Zhanjun Dong <zhanjun.dong@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Zhanjun Dong" <zhanjun.dong@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: [PATCH v4 0/1] drm/xe: Prevent null pointer access in xe_migrate_copy
Date: Fri, 27 Sep 2024 09:13:07 -0700	[thread overview]
Message-ID: <20240927161308.862323-1-zhanjun.dong@intel.com> (raw)

MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

xe_migrate_copy designed to copy content of TTM resources. When source
resource is null, it will trigger a NULL pointer dereference in
xe_migrate_copy. To avoid this situation, update lacks source flag to
true for this case, the flag will trigger xe_migrate_clear rather than
xe_migrate_copy.

Fixes: 266c85885263 ("drm/xe/xe2: Handle flat ccs move for igfx.")
Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>

Changes from prior revs:
 v4:- Limit commit message within 75 characters per line
      Minor commit message changes
 v3:- Update commit message to include Fixes and issue stack trace
 v2:- Drop changes in xe_migrate_copy
      Update condition expression as suggested

Zhanjun Dong (1):
  drm/xe: Prevent null pointer access in xe_migrate_copy

 drivers/gpu/drm/xe/xe_bo.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-09-27 16:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 16:13 Zhanjun Dong [this message]
2024-09-27 16:13 ` [PATCH v4 1/1] drm/xe: Prevent null pointer access in xe_migrate_copy Zhanjun Dong
2024-09-27 16:34   ` Matthew Auld
2024-09-27 16:43     ` Thomas Hellström
2024-09-30  7:46       ` Matthew Auld
2024-09-30 13:31         ` Dong, Zhanjun
2024-09-27 18:54 ` ✓ CI.Patch_applied: success for drm/xe: Prevent null pointer access in xe_migrate_copy (rev3) Patchwork
2024-09-27 18:55 ` ✓ CI.checkpatch: " Patchwork
2024-09-27 18:56 ` ✓ CI.KUnit: " Patchwork
2024-09-27 19:10 ` ✓ CI.Build: " Patchwork
2024-09-27 19:12 ` ✓ CI.Hooks: " Patchwork
2024-09-27 19:15 ` ✓ CI.checksparse: " Patchwork
2024-09-27 19:33 ` ✓ CI.BAT: " Patchwork
2024-09-30 23:35 ` ✗ CI.FULL: failure " Patchwork
2024-10-01  0:14   ` Dong, Zhanjun
2024-10-01 21:30     ` Matt Roper

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=20240927161308.862323-1-zhanjun.dong@intel.com \
    --to=zhanjun.dong@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=thomas.hellstrom@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox