From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Matthew Auld <matthew.auld@intel.com>
Subject: [Intel-xe] [PATCH v2 1/4] drm/xe: Ensure that we don't access the placements array out-of-bounds
Date: Thu, 23 Nov 2023 16:31:55 +0100 [thread overview]
Message-ID: <20231123153158.12779-2-thomas.hellstrom@linux.intel.com> (raw)
In-Reply-To: <20231123153158.12779-1-thomas.hellstrom@linux.intel.com>
Ensure, using xe_assert that the various try_add_<placement> functions
don't access the bo placements array out-of-bounds.
v2:
- Remove the places argument to make sure the xe_assert operates on
the array we're actually populating. (Matthew Auld)
Suggested-by: Ohad Sharabi <osharabi@habana.ai>
Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/946
Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
---
drivers/gpu/drm/xe/xe_bo.c | 39 +++++++++++++++++++++-----------------
1 file changed, 22 insertions(+), 17 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_bo.c b/drivers/gpu/drm/xe/xe_bo.c
index 4305f5cbc2ab..9bbb3d70ca21 100644
--- a/drivers/gpu/drm/xe/xe_bo.c
+++ b/drivers/gpu/drm/xe/xe_bo.c
@@ -121,11 +121,13 @@ static struct xe_mem_region *res_to_mem_region(struct ttm_resource *res)
return to_xe_ttm_vram_mgr(mgr)->vram;
}
-static void try_add_system(struct xe_bo *bo, struct ttm_place *places,
+static void try_add_system(struct xe_device *xe, struct xe_bo *bo,
u32 bo_flags, u32 *c)
{
+ xe_assert(xe, *c < ARRAY_SIZE(bo->placements));
+
if (bo_flags & XE_BO_CREATE_SYSTEM_BIT) {
- places[*c] = (struct ttm_place) {
+ bo->placements[*c] = (struct ttm_place) {
.mem_type = XE_PL_TT,
};
*c += 1;
@@ -170,26 +172,30 @@ static void add_vram(struct xe_device *xe, struct xe_bo *bo,
}
static void try_add_vram(struct xe_device *xe, struct xe_bo *bo,
- struct ttm_place *places, u32 bo_flags, u32 *c)
+ u32 bo_flags, u32 *c)
{
+ xe_assert(xe, *c < ARRAY_SIZE(bo->placements));
+
if (bo->props.preferred_gt == XE_GT1) {
if (bo_flags & XE_BO_CREATE_VRAM1_BIT)
- add_vram(xe, bo, places, bo_flags, XE_PL_VRAM1, c);
+ add_vram(xe, bo, bo->placements, bo_flags, XE_PL_VRAM1, c);
if (bo_flags & XE_BO_CREATE_VRAM0_BIT)
- add_vram(xe, bo, places, bo_flags, XE_PL_VRAM0, c);
+ add_vram(xe, bo, bo->placements, bo_flags, XE_PL_VRAM0, c);
} else {
if (bo_flags & XE_BO_CREATE_VRAM0_BIT)
- add_vram(xe, bo, places, bo_flags, XE_PL_VRAM0, c);
+ add_vram(xe, bo, bo->placements, bo_flags, XE_PL_VRAM0, c);
if (bo_flags & XE_BO_CREATE_VRAM1_BIT)
- add_vram(xe, bo, places, bo_flags, XE_PL_VRAM1, c);
+ add_vram(xe, bo, bo->placements, bo_flags, XE_PL_VRAM1, c);
}
}
static void try_add_stolen(struct xe_device *xe, struct xe_bo *bo,
- struct ttm_place *places, u32 bo_flags, u32 *c)
+ u32 bo_flags, u32 *c)
{
+ xe_assert(xe, *c < ARRAY_SIZE(bo->placements));
+
if (bo_flags & XE_BO_CREATE_STOLEN_BIT) {
- places[*c] = (struct ttm_place) {
+ bo->placements[*c] = (struct ttm_place) {
.mem_type = XE_PL_STOLEN,
.flags = bo_flags & (XE_BO_CREATE_PINNED_BIT |
XE_BO_CREATE_GGTT_BIT) ?
@@ -202,7 +208,6 @@ static void try_add_stolen(struct xe_device *xe, struct xe_bo *bo,
static int __xe_bo_placement_for_flags(struct xe_device *xe, struct xe_bo *bo,
u32 bo_flags)
{
- struct ttm_place *places = bo->placements;
u32 c = 0;
bo->props.preferred_mem_type = XE_BO_PROPS_INVALID;
@@ -210,22 +215,22 @@ static int __xe_bo_placement_for_flags(struct xe_device *xe, struct xe_bo *bo,
/* The order of placements should indicate preferred location */
if (bo->props.preferred_mem_class == DRM_XE_MEM_REGION_CLASS_SYSMEM) {
- try_add_system(bo, places, bo_flags, &c);
- try_add_vram(xe, bo, places, bo_flags, &c);
+ try_add_system(xe, bo, bo_flags, &c);
+ try_add_vram(xe, bo, bo_flags, &c);
} else {
- try_add_vram(xe, bo, places, bo_flags, &c);
- try_add_system(bo, places, bo_flags, &c);
+ try_add_vram(xe, bo, bo_flags, &c);
+ try_add_system(xe, bo, bo_flags, &c);
}
- try_add_stolen(xe, bo, places, bo_flags, &c);
+ try_add_stolen(xe, bo, bo_flags, &c);
if (!c)
return -EINVAL;
bo->placement = (struct ttm_placement) {
.num_placement = c,
- .placement = places,
+ .placement = bo->placements,
.num_busy_placement = c,
- .busy_placement = places,
+ .busy_placement = bo->placements,
};
return 0;
--
2.41.0
next prev parent reply other threads:[~2023-11-23 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 15:31 [Intel-xe] [PATCH v2 0/4] drm/xe: Assorted memory-management fixes Thomas Hellström
2023-11-23 15:31 ` Thomas Hellström [this message]
2023-11-23 15:34 ` [Intel-xe] [PATCH v2 1/4] drm/xe: Ensure that we don't access the placements array out-of-bounds Matthew Auld
2023-11-23 15:31 ` [Intel-xe] [PATCH v2 2/4] drm/xe/bo: Rename xe_bo_get_sg() to xe_bo_sg() Thomas Hellström
2023-11-23 15:31 ` [Intel-xe] [PATCH v2 3/4] drm/xe/bo: Remove leftover trace_printk() Thomas Hellström
2023-11-23 15:31 ` [Intel-xe] [PATCH v2 4/4] drm/xe/vm: Fix ASID XA usage Thomas Hellström
2023-11-23 16:01 ` Matthew Auld
2023-11-24 9:04 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Assorted memory-management fixes (rev2) Patchwork
2023-11-24 9:04 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-11-24 9:06 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-11-24 9:13 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-24 9:13 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-11-24 9:14 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-11-24 9:48 ` [Intel-xe] ✓ CI.BAT: " 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=20231123153158.12779-2-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@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