summaryrefslogtreecommitdiff
path: root/flowtop
diff options
context:
space:
mode:
authorVadim Kochan <vadim4j@gmail.com>2015-05-05 10:44:57 +0300
committerTobias Klauser <tklauser@distanz.ch>2015-05-05 11:55:29 +0200
commit0757f825dd4b0e3653a98264bbe3933d54b3c1ef (patch)
tree8b4bb216ab0460baa32b465808925123369ae854 /flowtop
parentd245603ab331de51d774f3d69ba3689155b0eb53 (diff)
tprintf: Fix color breaking in less mode
Automatic new line indentation can break terminal ESC color sequence by inserting new line within it. Fixed by considering that color ESC sequence is not closed by 'm' and only after it is closed - print new line with spaces. Signed-off-by: Vadim Kochan <vadim4j@gmail.com> [tk: add comments] Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'flowtop')
0 files changed, 0 insertions, 0 deletions
' 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 'net/xfrm/xfrm_sysctl.c')