summaryrefslogtreecommitdiff
path: root/net/ieee802154/6lowpan
diff options
context:
space:
mode:
authorGary R Hook <gary.hook@amd.com>2017-01-27 17:09:04 -0600
committerHerbert Xu <herbert@gondor.apana.org.au>2017-02-03 17:45:46 +0800
commite5da5c5667381d2772374ee6a2967b3576c9483d (patch)
tree426bc8a0a32233f28da1fa913e99b4a6c30b64db /net/ieee802154/6lowpan
parent500c0106e638e08c2c661c305ed57d6b67e10908 (diff)
crypto: ccp - Fix double add when creating new DMA command
Eliminate a double-add by creating a new list to manage command descriptors when created; move the descriptor to the pending list when the command is submitted. Cc: <stable@vger.kernel.org> Signed-off-by: Gary R Hook <gary.hook@amd.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'net/ieee802154/6lowpan')
0 files changed, 0 insertions, 0 deletions
gt;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 'tools/perf/scripts/perl/bin/wakeup-latency-report')