mlxsw: reg: Add Policy-Engine ACL Register - net-next.git - net-next plumbings

summary refs log tree commit diff

path: root/sound/soc/mxs/mxs-saif.c

diff options

author	Jiri Pirko <jiri@mellanox.com>	2017-02-03 10:28:53 +0100
committer	David S. Miller <davem@davemloft.net>	2017-02-03 16:35:38 -0500
commit	3279da4c8877357b1001b4a3359069d588053f27 (patch)
tree	1d34053698f43317c19aedc70211d8ff75ee0ec3 /sound/soc/mxs/mxs-saif.c
parent	d5e556c6a158893d9e50de3d4e7638f753ffd520 (diff)

mlxsw: reg: Add Policy-Engine ACL Register

The PACL register is used for configuration of the ACL. Signed-off-by: Jiri Pirko <jiri@mellanox.com> Reviewed-by: Ido Schimmel <idosch@mellanox.com> Signed-off-by: David S. Miller <davem@davemloft.net>

Diffstat (limited to 'sound/soc/mxs/mxs-saif.c')

0 files changed, 0 insertions, 0 deletions

ree_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 'security/integrity/ima/ima_crypto.c')