mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yang Yingliang <yangyingliang@huawei.com>
To: <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Cc: <baruch@tkos.co.il>, <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 4.9/4.14/4.19/5.4] tty/serial: digicolor: fix possible null-ptr-deref in digicolor_uart_probe()
Date: Mon, 16 May 2022 22:01:41 +0800	[thread overview]
Message-ID: <3580ada7-3ad8-2caa-8af2-32896b752f2f@huawei.com> (raw)
In-Reply-To: <20220516141053.1549344-1-yangyingliang@huawei.com>

I use a wrong commit id, please ignore this patch.

On 2022/5/16 22:10, Yang Yingliang wrote:
> commit 7c25a0b89a487878b0691e6524fb5a8827322194 upstream.
>
> It will cause null-ptr-deref when using 'res', if platform_get_resource()
> returns NULL, so move using 'res' after devm_ioremap_resource() that
> will check it to avoid null-ptr-deref.
> And use devm_platform_get_and_ioremap_resource() to simplify code.
>
> Fixes: 5930cb3511df ("serial: driver for Conexant Digicolor USART")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> Reviewed-by: Baruch Siach <baruch@tkos.co.il>
> Cc: stable <stable@vger.kernel.org>
> Link: https://lore.kernel.org/r/20220505124621.1592697-1-yangyingliang@huawei.com
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> v1:
>    These stable versions don't have devm_platform_get_and_ioremap_resource(),
>    so just move using 'res' after devm_ioremap_resource().
> ---
>   drivers/tty/serial/digicolor-usart.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/digicolor-usart.c b/drivers/tty/serial/digicolor-usart.c
> index 50ec5f1ac77f4..794864fac6250 100644
> --- a/drivers/tty/serial/digicolor-usart.c
> +++ b/drivers/tty/serial/digicolor-usart.c
> @@ -476,10 +476,10 @@ static int digicolor_uart_probe(struct platform_device *pdev)
>   		return PTR_ERR(uart_clk);
>   
>   	res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> -	dp->port.mapbase = res->start;
>   	dp->port.membase = devm_ioremap_resource(&pdev->dev, res);
>   	if (IS_ERR(dp->port.membase))
>   		return PTR_ERR(dp->port.membase);
> +	dp->port.mapbase = res->start;
>   
>   	irq = platform_get_irq(pdev, 0);
>   	if (irq < 0)

  reply	other threads:[~2022-05-16 14:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 14:10 Yang Yingliang
2022-05-16 14:01 ` Yang Yingliang [this message]
2022-05-16 14:11 Yang Yingliang
2022-05-16 15:26 ` Greg KH

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=3580ada7-3ad8-2caa-8af2-32896b752f2f@huawei.com \
    --to=yangyingliang@huawei.com \
    --cc=baruch@tkos.co.il \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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

all inboxes | Powered by JetHome®