summaryrefslogtreecommitdiff
path: root/contrib/dissector_fuzz.sh
diff options
context:
space:
mode:
authorKartik Mistry <kartik.mistry@gmail.com>2018-12-10 09:56:15 +0530
committerTobias Klauser <tobias.klauser@gmail.com>2018-12-10 13:41:09 +0100
commit1b966299df22a429d041e86300c928bb61d63ba5 (patch)
treecc608ae3b0dc7af35b16975e8d3fa06b16bf84bf /contrib/dissector_fuzz.sh
parenta91876c4306e72765ab6f87c2adab986ab4f1193 (diff)
Fix manpage warnings
Signed-off-by: Kartik Mistry <kartik.mistry@gmail.com>
Diffstat (limited to 'contrib/dissector_fuzz.sh')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-02-23 07:45:06 +0000
lock by acquiring a different lock than `dma_pl330_rqcb'. NOTE that, as a result, `pl330_free_chan_resources' executes `list_splice_tail_init' on `pch->work_list' under lock `pl330->lock', whereas in the rest of the code `pch->work_list' is protected by `pch->lock'. I don't know if this may cause race conditions. Similarly `pch->cyclic' is written by `pl330_alloc_chan_resources' under `pl330->lock' but read by `pl330_tx_submit' under `pch->lock'. Second, I have removed locking from `pl330_request_channel' and `pl330_release_channel' functions. Function `pl330_request_channel' is only called from `pl330_alloc_chan_resources', so the lock is already held. Function `pl330_release_channel' is called from `pl330_free_chan_resources', which already holds the lock, and from `pl330_del'. Function `pl330_del' is called in an error path of `pl330_probe' and at the end of `pl330_remove', but I assume that there cannot be concurrent accesses to the protected data at those points. Signed-off-by: Iago Abal <mail@iagoabal.eu> Reviewed-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'sound/soc/intel/skylake/skl-topology.c')