public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/5] drm/i915/dpll: replace BUG_ON() with drm_WARN_ON()
Date: Fri, 26 Aug 2022 14:08:22 +0300	[thread overview]
Message-ID: <Ywippo6I1KprqxZc@intel.com> (raw)
In-Reply-To: <e2e92085888815e4f47ea117cc43499e595f3161.1661503049.git.jani.nikula@intel.com>

On Fri, Aug 26, 2022 at 11:38:14AM +0300, Jani Nikula wrote:
> Avoid BUG_ON(). Actually check the dpll count and bail out loudly with
> drm_WARN_ON() from the loop before overflowing
> i915->dpll.shared_dplls[].
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_dpll_mgr.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_dpll_mgr.c b/drivers/gpu/drm/i915/display/intel_dpll_mgr.c
> index 118598c9a809..8dd405553cfa 100644
> --- a/drivers/gpu/drm/i915/display/intel_dpll_mgr.c
> +++ b/drivers/gpu/drm/i915/display/intel_dpll_mgr.c
> @@ -4199,6 +4199,10 @@ void intel_shared_dpll_init(struct drm_i915_private *dev_priv)
>  	dpll_info = dpll_mgr->dpll_info;
>  
>  	for (i = 0; dpll_info[i].name; i++) {
> +		if (drm_WARN_ON(&dev_priv->drm,
> +				i >= ARRAY_SIZE(dev_priv->dpll.shared_dplls)))
> +			break;

Shame we can't neatly use a BUILD_BUG_ON() when assigning .dpll_info.

For patches 2-5
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> +
>  		drm_WARN_ON(&dev_priv->drm, i != dpll_info[i].id);
>  		dev_priv->dpll.shared_dplls[i].info = &dpll_info[i];
>  	}
> @@ -4206,8 +4210,6 @@ void intel_shared_dpll_init(struct drm_i915_private *dev_priv)
>  	dev_priv->dpll.mgr = dpll_mgr;
>  	dev_priv->dpll.num_shared_dpll = i;
>  	mutex_init(&dev_priv->dpll.lock);
> -
> -	BUG_ON(dev_priv->dpll.num_shared_dpll > I915_NUM_PLLS);
>  }
>  
>  /**
> -- 
> 2.34.1

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2022-08-26 11:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  8:38 [Intel-gfx] [PATCH 0/5] drm/i915: some BUG_ON() removals Jani Nikula
2022-08-26  8:38 ` [Intel-gfx] [PATCH 1/5] drm/i915/crt: replace BUG_ON() with drm_WARN_ON() Jani Nikula
2022-08-26 10:59   ` Ville Syrjälä
2022-08-26  8:38 ` [Intel-gfx] [PATCH 2/5] drm/i915/dpll: " Jani Nikula
2022-08-26 11:08   ` Ville Syrjälä [this message]
2022-08-26  8:38 ` [Intel-gfx] [PATCH 3/5] drm/i915/pch: " Jani Nikula
2022-08-26  8:38 ` [Intel-gfx] [PATCH 4/5] drm/i915/perf: replace BUG_ON() with WARN_ON() Jani Nikula
2022-08-26  8:38 ` [Intel-gfx] [PATCH 5/5] drm/i915/fence: replace BUG_ON() with BUILD_BUG_ON() Jani Nikula
2022-08-26 10:07 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: some BUG_ON() removals Patchwork
2022-08-26 10:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-08-30 11:24 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=Ywippo6I1KprqxZc@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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