* Possible memory leak in cafe_ccic.ko
@ 2017-08-22 16:26 Anton Volkov
0 siblings, 0 replies; only message in thread
From: Anton Volkov @ 2017-08-22 16:26 UTC (permalink / raw)
To: corbet
Cc: mchehab, linux-media, linux-kernel, ldv-project, Alexey Khoroshilov
Hello.
While searching for races in the Linux kernel I've come across
"drivers/media/platform/marvell-ccic/cafe_ccic.ko" module. Here are
questions that I came up with while analyzing results. Lines are given
using the info from Linux v4.12.
Consider the following case:
Thread 1: Thread 2:
mcam_v4l_release
->mcam_free_dma_bufs
cam->dma_bufs[i] = NULL
cam->nbufs = 0
cafe_pci_resume (mcam-core.c: line 413)
->mccic_resume
->mcam_read_setup
->mcam_alloc_dma_bufs
cam->dma_bufs[i] =
dma_alloc_coherent()
(mcam-core.c: line 381)
It looks like mcam_v4l_release() doesn't really shut the device down. In
this case cafe_pci_resume() leaks memory for cam->dma_bufs[i] after
mcam_v4l_release() freed and poisoned them. Is this feasible from your
point of view?
Thank you for your time.
-- Anton Volkov
Linux Verification Center, ISPRAS
web: http://linuxtesting.org
e-mail: avolkov@ispras.ru
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-08-22 16:26 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-08-22 16:26 Possible memory leak in cafe_ccic.ko Anton Volkov
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).