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>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Himal Prasad Ghimiray" <himal.prasad.ghimiray@intel.com>,
	"Matt Roper" <matthew.d.roper@intel.com>
Subject: [PATCH v3 0/1] drm/xe: Prevent null pointer access in xe_migrate_copy
Date: Tue, 24 Sep 2024 18:21:09 -0700	[thread overview]
Message-ID: <20240925012110.493257-1-zhanjun.dong@intel.com> (raw)

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

Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Cc: Matt Roper <matthew.d.roper@intel.com>

Changes from prior revs:
 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-25  1:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25  1:21 Zhanjun Dong [this message]
2024-09-25  1:21 ` [PATCH v3 1/1] drm/xe: Prevent null pointer access in xe_migrate_copy Zhanjun Dong
2024-09-26 20:00   ` Thomas Hellström
2024-09-26 21:41     ` Dong, Zhanjun
2024-09-26  5:37 ` ✓ CI.Patch_applied: success for drm/xe: Prevent null pointer access in xe_migrate_copy (rev2) Patchwork
2024-09-26  5:37 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-26  5:38 ` ✓ CI.KUnit: success " Patchwork
2024-09-26  5:49 ` ✓ CI.Build: " Patchwork
2024-09-26  5:52 ` ✓ CI.Hooks: " Patchwork
2024-09-26  5:53 ` ✓ CI.checksparse: " Patchwork
2024-09-26  6:32 ` ✗ CI.BAT: failure " Patchwork
2024-09-26 13:53   ` Dong, Zhanjun
2024-09-26 18:20 ` ✗ CI.FULL: " Patchwork
2024-09-26 19:00   ` Dong, Zhanjun

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=20240925012110.493257-1-zhanjun.dong@intel.com \
    --to=zhanjun.dong@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=matthew.d.roper@intel.com \
    --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