From: Colin Ian King <colin.king@canonical.com>
To: Michael Walle <michael@walle.cc>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: tty: serial: fsl_lpuart: fix DMA mapping - static analysis bug report
Date: Fri, 3 Apr 2020 14:13:05 +0100 [thread overview]
Message-ID: <abbbbe20-95d5-e1b1-0538-68a4c7d0c8d6@canonical.com> (raw)
In-Reply-To: <ba294a2b336b3cde9f5fd2ddbf1fe490@walle.cc>
On 03/04/2020 14:05, Michael Walle wrote:
> Am 2020-04-03 14:44, schrieb Colin Ian King:
>> Hi,
>>
>> Static analysis with Coverity has found an issue with the following
>> commit:
>>
>> From a092ab25fdaa445b821f5959e458350696fce44c Mon Sep 17 00:00:00 2001
>> From: Michael Walle <michael@walle.cc>
>> Date: Fri, 6 Mar 2020 22:44:31 +0100
>> Subject: [PATCH] tty: serial: fsl_lpuart: fix DMA mapping
>>
>> The analysis report is as follows for function lpuart_dma_rx_free in
>> source drivers/tty/serial/fsl_lpuart.c :
>>
>> var_compare_op: Comparing chan to null implies that chan might be null.
>>
>> 1234 if (chan)
>> 1235 dmaengine_terminate_all(chan);
>> 1236
>>
>> Dereference after null check (FORWARD_NULL)
>> var_deref_op: Dereferencing null pointer chan.
>>
>> 1237 dma_unmap_sg(chan->device->dev, &sport->rx_sgl, 1,
>> DMA_FROM_DEVICE);
>>
>> The check for chan being null implies it is may be null, however, the
>> call to dma_unmap_sg dereferences chan which leads to a null pointer
>> dereference issue.
>
> Technically, this is correct. But lpuart_dma_rx_free() is guarded by
> lpuart_dma_rx_use which is only true if there is a dma channel, see
> lpuart_rx_dma_startup(). In any way, this looks bogus.
>
> So actually, the "if (chan)" is superfluous. Could you double check that?
> Then I'd make a patch which removes the if (chan) to make coverity happy.
Yep, I've eyeballed the code and all the calls to the
lpuart_dma_rx_free() check lpuart_dma_rx_use is true before the call, so
it does appear the if (chan) check is superfluous.
Colin
>
> -michael
prev parent reply other threads:[~2020-04-03 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 12:44 Colin Ian King
2020-04-03 13:05 ` Michael Walle
2020-04-03 13:13 ` Colin Ian King [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=abbbbe20-95d5-e1b1-0538-68a4c7d0c8d6@canonical.com \
--to=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=michael@walle.cc \
/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®