summaryrefslogtreecommitdiff
path: root/mausezahn/Makefile
diff options
context:
space:
mode:
authorVadim Kochan <vadim4j@gmail.com>2015-05-19 17:10:38 +0300
committerDaniel Borkmann <daniel@iogearbox.net>2015-06-01 01:18:25 +0200
commit107456c646ab38e5ccb6ee788389faced59c16ff (patch)
tree4db201d48c9078e72ad89d126fe396f1fe685306 /mausezahn/Makefile
parentd0677020ce89fc087925467480d75428df52dc95 (diff)
netsniff-ng, nlmsg: Dissect rtnl link type messages
Dump RTnetlink interface related info with attributes. Signed-off-by: Vadim Kochan <vadim4j@gmail.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Diffstat (limited to 'mausezahn/Makefile')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-03-03 10:02:19 +0000
e 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/selinux/netlink.c')