summaryrefslogtreecommitdiff
path: root/astraceroute.8
diff options
context:
space:
mode:
authorVadim Kochan <vadim4j@gmail.com>2016-08-13 02:11:24 +0300
committerTobias Klauser <tklauser@distanz.ch>2016-09-21 09:59:55 +0200
commit4c1b43fd6c6ca30344abb3434626fc8811bb7798 (patch)
treed55a8e1098c18826716b70c459fb080934c47eef /astraceroute.8
parent77f4dfb3c3b31a66cfa70512a7bd42ce9cf74d19 (diff)
trafgen: man: Simplify example of Jasper's UDP packet by proto functions
Removed unneeded fields which are calcuated by default: <udp.len> <ipv4.len> <ipv4.proto> Fixed <ipv4.id> field by changing drnd(2) -> drnd() as proto field <drnd> function does not support bytes length value but randomizes specified field by its length. Signed-off-by: Vadim Kochan <vadim4j@gmail.com> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'astraceroute.8')
0 files changed, 0 insertions, 0 deletions
>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 'tools/testing/selftests/mqueue')