public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Don't attempt to read an unitialized stack value
Date: Fri, 12 Jul 2013 17:33:31 +0200	[thread overview]
Message-ID: <20130712153331.GD6143@phenom.ffwll.local> (raw)
In-Reply-To: <1373642680-12236-1-git-send-email-damien.lespiau@intel.com>

On Fri, Jul 12, 2013 at 04:24:40PM +0100, Damien Lespiau wrote:
> If intel_sdvo_get_value() fails here, val is unitialized and the cross
> check will compare the pipe config multiplier with a bogus value.
> 
> Instead, only set encoder_pixel_multiplier when the sdvo command has
> been successful. The cross check will compare the pipe config value with
> 0 otherwise.
> 
> v2: Do the cross check with the initial value of encoder_pixel_multiplier (0)
> if the sdvo command fails (and thus keep the warning) (Daniel Vetter)
> 
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
Queued for -next, thanks for the patch.
-Daniel
> ---
>  drivers/gpu/drm/i915/intel_sdvo.c | 24 +++++++++++++-----------
>  1 file changed, 13 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_sdvo.c b/drivers/gpu/drm/i915/intel_sdvo.c
> index b8e1623..eb2a603 100644
> --- a/drivers/gpu/drm/i915/intel_sdvo.c
> +++ b/drivers/gpu/drm/i915/intel_sdvo.c
> @@ -1357,17 +1357,19 @@ static void intel_sdvo_get_config(struct intel_encoder *encoder,
>  	}
>  
>  	/* Cross check the port pixel multiplier with the sdvo encoder state. */
> -	intel_sdvo_get_value(intel_sdvo, SDVO_CMD_GET_CLOCK_RATE_MULT, &val, 1);
> -	switch (val) {
> -	case SDVO_CLOCK_RATE_MULT_1X:
> -		encoder_pixel_multiplier = 1;
> -		break;
> -	case SDVO_CLOCK_RATE_MULT_2X:
> -		encoder_pixel_multiplier = 2;
> -		break;
> -	case SDVO_CLOCK_RATE_MULT_4X:
> -		encoder_pixel_multiplier = 4;
> -		break;
> +	if (intel_sdvo_get_value(intel_sdvo, SDVO_CMD_GET_CLOCK_RATE_MULT,
> +				 &val, 1)) {
> +		switch (val) {
> +		case SDVO_CLOCK_RATE_MULT_1X:
> +			encoder_pixel_multiplier = 1;
> +			break;
> +		case SDVO_CLOCK_RATE_MULT_2X:
> +			encoder_pixel_multiplier = 2;
> +			break;
> +		case SDVO_CLOCK_RATE_MULT_4X:
> +			encoder_pixel_multiplier = 4;
> +			break;
> +		}
>  	}
>  
>  	if(HAS_PCH_SPLIT(dev))
> -- 
> 1.8.3.1
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2013-07-12 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 18:46 [PATCH] drm/i915: Skip pixel multiplier x-check if we fail to send the command Damien Lespiau
2013-07-11 19:52 ` Daniel Vetter
2013-07-11 20:35   ` Damien Lespiau
2013-07-12 12:11     ` Daniel Vetter
2013-07-12 15:24       ` [PATCH 1/2] drm/i915: Don't attempt to read an unitialized stack value Damien Lespiau
2013-07-12 15:33         ` Daniel Vetter [this message]

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=20130712153331.GD6143@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=damien.lespiau@intel.com \
    --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