linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] video: fbdev: fsl: fix kernel crash when diu_ops is not implemented
Date: Tue, 24 Nov 2015 10:46:14 +0000	[thread overview]
Message-ID: <56543FF6.2050807@ti.com> (raw)
In-Reply-To: <1448346450-47403-1-git-send-email-dongsheng.wang@freescale.com>

[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]



On 24/11/15 08:27, Dongsheng Wang wrote:
> From: Wang Dongsheng <dongsheng.wang@freescale.com>
> 
> If diu_ops is not implemented on platform, kernel will access a null
> pointer. we need to check this pointer in diu initialization.
> 
> Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
> 
> diff --git a/drivers/video/fbdev/fsl-diu-fb.c b/drivers/video/fbdev/fsl-diu-fb.c
> index b335c1a..288b5e4 100644
> --- a/drivers/video/fbdev/fsl-diu-fb.c
> +++ b/drivers/video/fbdev/fsl-diu-fb.c
> @@ -479,7 +479,10 @@ static enum fsl_diu_monitor_port fsl_diu_name_to_port(const char *s)
>  			port = FSL_DIU_PORT_DLVDS;
>  	}
>  
> -	return diu_ops.valid_monitor_port(port);
> +	if (diu_ops.valid_monitor_port)
> +		port = diu_ops.valid_monitor_port(port);
> +
> +	return port;
>  }
>  
>  /*
> @@ -1697,6 +1700,9 @@ static int fsl_diu_probe(struct platform_device *pdev)
>  	unsigned int i;
>  	int ret;
>  
> +	if (!diu_ops.set_pixel_clock)
> +		return -ENODEV;
> +
>  	data = dmam_alloc_coherent(&pdev->dev, sizeof(struct fsl_diu_data),
>  				   &dma_addr, GFP_DMA | __GFP_ZERO);
>  	if (!data)
> 

Thanks, queued for 4.5.

 Tomi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-11-24 10:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24  6:27 [PATCH] video: fbdev: fsl: fix kernel crash when diu_ops is not implemented Dongsheng Wang
2015-11-24 10:46 ` Tomi Valkeinen [this message]
2015-11-24 11:01 ` Wang Dongsheng
2015-11-24 16:04 ` Timur Tabi
2015-11-24 16:12 ` Timur Tabi
2015-11-24 16:15 ` Scott Wood
2015-11-24 16:15 ` Tomi Valkeinen
2015-11-24 16:54 ` Timur Tabi
2015-11-24 16:55 ` Scott Wood
2015-11-24 16:56 ` Timur Tabi
2015-11-24 16:57 ` Wang Dongsheng
2015-11-24 16:59 ` Scott Wood
2015-11-24 17:00 ` Scott Wood
2015-11-24 17:02 ` Timur Tabi
2015-11-24 17:02 ` Wang Dongsheng
2015-11-24 17:05 ` Timur Tabi
2015-11-24 17:05 ` Scott Wood
2015-11-24 17:06 ` Timur Tabi
2015-11-24 17:10 ` Scott Wood
2015-11-24 17:16 ` Timur Tabi
2015-11-24 17:17 ` Scott Wood
2015-12-01  8:43 ` Wang Dongsheng
2015-12-01 14:53 ` Timur Tabi

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=56543FF6.2050807@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-fbdev@vger.kernel.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).