* Coverity: meson_cipher(): RESOURCE_LEAK
@ 2019-11-04 17:35 coverity-bot
2019-11-05 19:10 ` LABBE Corentin
0 siblings, 1 reply; 2+ messages in thread
From: coverity-bot @ 2019-11-04 17:35 UTC (permalink / raw)
To: Corentin Labbe
Cc: Neil Armstrong, Herbert Xu, Gustavo A. R. Silva, linux-next
Hello!
This is an experimental automated report about issues detected by Coverity
from a scan of next-20191031 as part of the linux-next weekly scan project:
https://scan.coverity.com/projects/linux-next-weekly-scan
You're getting this email because you were associated with the identified
lines of code (noted below) that were touched by recent commits:
48fe583fe541 ("crypto: amlogic - Add crypto accelerator for amlogic GXL")
Coverity reported the following:
*** CID 1487403: (RESOURCE_LEAK)
/drivers/crypto/amlogic/amlogic-gxl-cipher.c: 258 in meson_cipher()
252 ivsize, 0);
253 }
254 }
255 theend:
256 kzfree(bkeyiv);
257
vvv CID 1487403: (RESOURCE_LEAK)
vvv Variable "backup_iv" going out of scope leaks the storage it points to.
258 return err;
259 }
260
261 static int meson_handle_cipher_request(struct crypto_engine *engine,
262 void *areq)
263 {
/drivers/crypto/amlogic/amlogic-gxl-cipher.c: 156 in meson_cipher()
150 keyivlen = 32;
151
152 phykeyiv = dma_map_single(mc->dev, bkeyiv, keyivlen,
153 DMA_TO_DEVICE);
154 if (dma_mapping_error(mc->dev, phykeyiv)) {
155 dev_err(mc->dev, "Cannot DMA MAP KEY IV\n");
vvv CID 1487403: (RESOURCE_LEAK)
vvv Variable "backup_iv" going out of scope leaks the storage it points to.
156 return -EFAULT;
157 }
158
159 tloffset = 0;
160 eat = 0;
161 i = 0;
If this is a false positive, please let us know so we can mark it as
such, or teach the Coverity rules to be smarter. If not, please make
sure fixes get into linux-next. :) For patches fixing this, please
include these lines (but double-check the "Fixes" first):
Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
Addresses-Coverity-ID: 1487403 ("RESOURCE_LEAK")
Fixes: 48fe583fe541 ("crypto: amlogic - Add crypto accelerator for amlogic GXL")
Thanks for your attention!
--
Coverity-bot
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Coverity: meson_cipher(): RESOURCE_LEAK
2019-11-04 17:35 Coverity: meson_cipher(): RESOURCE_LEAK coverity-bot
@ 2019-11-05 19:10 ` LABBE Corentin
0 siblings, 0 replies; 2+ messages in thread
From: LABBE Corentin @ 2019-11-05 19:10 UTC (permalink / raw)
To: coverity-bot; +Cc: Neil Armstrong, Herbert Xu, Gustavo A. R. Silva, linux-next
On Mon, Nov 04, 2019 at 09:35:05AM -0800, coverity-bot wrote:
> Hello!
>
> This is an experimental automated report about issues detected by Coverity
> from a scan of next-20191031 as part of the linux-next weekly scan project:
> https://scan.coverity.com/projects/linux-next-weekly-scan
>
> You're getting this email because you were associated with the identified
> lines of code (noted below) that were touched by recent commits:
>
> 48fe583fe541 ("crypto: amlogic - Add crypto accelerator for amlogic GXL")
>
> Coverity reported the following:
>
> *** CID 1487403: (RESOURCE_LEAK)
> /drivers/crypto/amlogic/amlogic-gxl-cipher.c: 258 in meson_cipher()
> 252 ivsize, 0);
> 253 }
> 254 }
> 255 theend:
> 256 kzfree(bkeyiv);
> 257
> vvv CID 1487403: (RESOURCE_LEAK)
> vvv Variable "backup_iv" going out of scope leaks the storage it points to.
> 258 return err;
> 259 }
> 260
> 261 static int meson_handle_cipher_request(struct crypto_engine *engine,
> 262 void *areq)
> 263 {
> /drivers/crypto/amlogic/amlogic-gxl-cipher.c: 156 in meson_cipher()
> 150 keyivlen = 32;
> 151
> 152 phykeyiv = dma_map_single(mc->dev, bkeyiv, keyivlen,
> 153 DMA_TO_DEVICE);
> 154 if (dma_mapping_error(mc->dev, phykeyiv)) {
> 155 dev_err(mc->dev, "Cannot DMA MAP KEY IV\n");
> vvv CID 1487403: (RESOURCE_LEAK)
> vvv Variable "backup_iv" going out of scope leaks the storage it points to.
> 156 return -EFAULT;
> 157 }
> 158
> 159 tloffset = 0;
> 160 eat = 0;
> 161 i = 0;
>
> If this is a false positive, please let us know so we can mark it as
> such, or teach the Coverity rules to be smarter. If not, please make
> sure fixes get into linux-next. :) For patches fixing this, please
> include these lines (but double-check the "Fixes" first):
>
> Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
> Addresses-Coverity-ID: 1487403 ("RESOURCE_LEAK")
> Fixes: 48fe583fe541 ("crypto: amlogic - Add crypto accelerator for amlogic GXL")
>
>
> Thanks for your attention!
>
I will send the fix soon.
Thanks
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-11-05 19:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-04 17:35 Coverity: meson_cipher(): RESOURCE_LEAK coverity-bot
2019-11-05 19:10 ` LABBE Corentin
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).