intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/4] drm/i915: Do not define vma on stack
Date: Wed, 4 Aug 2021 19:37:49 +0000	[thread overview]
Message-ID: <20210804193749.GA87546@DUT151-ICLU.fm.intel.com> (raw)
In-Reply-To: <20210803051121.72017-2-matthew.brost@intel.com>

On Mon, Aug 02, 2021 at 10:11:18PM -0700, Matthew Brost wrote:
> From: Venkata Sandeep Dhanalakota <venkata.s.dhanalakota@intel.com>
> 
> Defining vma on stack can cause stack overflow, if
> vma gets populated with new fields.
> 
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Signed-off-by: Venkata Sandeep Dhanalakota <venkata.s.dhanalakota@intel.com>
> Signef-off-by: Matthew Brost <matthew.brost@intel.com>

Reviewed-by: Matthew Brost <matthew.brost@intel.com>

> ---
>  drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 18 +++++++++---------
>  drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h |  2 ++
>  2 files changed, 11 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> index 3a16d08608a5..f632dbd32b42 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> @@ -413,20 +413,20 @@ static void uc_fw_bind_ggtt(struct intel_uc_fw *uc_fw)
>  {
>  	struct drm_i915_gem_object *obj = uc_fw->obj;
>  	struct i915_ggtt *ggtt = __uc_fw_to_gt(uc_fw)->ggtt;
> -	struct i915_vma dummy = {
> -		.node.start = uc_fw_ggtt_offset(uc_fw),
> -		.node.size = obj->base.size,
> -		.pages = obj->mm.pages,
> -		.vm = &ggtt->vm,
> -	};
> +	struct i915_vma *dummy = &uc_fw->dummy;
> +
> +	dummy->node.start = uc_fw_ggtt_offset(uc_fw);
> +	dummy->node.size = obj->base.size;
> +	dummy->pages = obj->mm.pages;
> +	dummy->vm = &ggtt->vm;
>  
>  	GEM_BUG_ON(!i915_gem_object_has_pinned_pages(obj));
> -	GEM_BUG_ON(dummy.node.size > ggtt->uc_fw.size);
> +	GEM_BUG_ON(dummy->node.size > ggtt->uc_fw.size);
>  
>  	/* uc_fw->obj cache domains were not controlled across suspend */
> -	drm_clflush_sg(dummy.pages);
> +	drm_clflush_sg(dummy->pages);
>  
> -	ggtt->vm.insert_entries(&ggtt->vm, &dummy, I915_CACHE_NONE, 0);
> +	ggtt->vm.insert_entries(&ggtt->vm, dummy, I915_CACHE_NONE, 0);
>  }
>  
>  static void uc_fw_unbind_ggtt(struct intel_uc_fw *uc_fw)
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h
> index 99bb1fe1af66..693cc0ebcd63 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h
> @@ -10,6 +10,7 @@
>  #include "intel_uc_fw_abi.h"
>  #include "intel_device_info.h"
>  #include "i915_gem.h"
> +#include "i915_vma.h"
>  
>  struct drm_printer;
>  struct drm_i915_private;
> @@ -75,6 +76,7 @@ struct intel_uc_fw {
>  	bool user_overridden;
>  	size_t size;
>  	struct drm_i915_gem_object *obj;
> +	struct i915_vma dummy;
>  
>  	/*
>  	 * The firmware build process will generate a version header file with major and
> -- 
> 2.28.0
> 

  reply	other threads:[~2021-08-04 19:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03  5:11 [Intel-gfx] [PATCH 0/4] Enable GuC submission by default on DG1 Matthew Brost
2021-08-03  5:04 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-08-03  5:05 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-03  5:11 ` [Intel-gfx] [PATCH 1/4] drm/i915: Do not define vma on stack Matthew Brost
2021-08-04 19:37   ` Matthew Brost [this message]
2021-08-03  5:11 ` [Intel-gfx] [PATCH 2/4] drm/i915/guc: put all guc objects in lmem when available Matthew Brost
2021-08-06 18:43   ` John Harrison
2021-08-03  5:11 ` [Intel-gfx] [PATCH 3/4] drm/i915/guc: Add DG1 GuC / HuC firmware defs Matthew Brost
2021-08-06 18:43   ` John Harrison
2021-08-03  5:11 ` [Intel-gfx] [PATCH 4/4] drm/i915/guc: Enable GuC submission by default on DG1 Matthew Brost
2021-08-06 18:44   ` John Harrison
2021-08-03  5:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-08-03 12:15 ` [Intel-gfx] [PATCH 0/4] " Daniel Vetter
2021-08-03 17:26   ` Matthew Brost
2021-08-06 11:34     ` Thomas Hellström (Intel)
2021-08-06 12:07       ` Thomas Hellström (Intel)
2021-08-06 16:09       ` Thomas Hellström (Intel)
2021-08-07 17:20       ` Matthew Brost
2021-08-03 16:22 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=20210804193749.GA87546@DUT151-ICLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /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;
as well as URLs for NNTP newsgroup(s).