summaryrefslogtreecommitdiff
path: root/flowtop/.gitignore
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2013-11-25 09:24:05 +0100
committerTobias Klauser <tklauser@distanz.ch>2013-11-25 09:24:05 +0100
commitb9c04d953676c63c9e069a9ada1bb589860b470b (patch)
treeb0f1034a5fa6635e01e836dca137e8418f9d47b7 /flowtop/.gitignore
parent8dcdd694e879451d7b68e45587772757f8d7da87 (diff)
bpfc: Check return value of system()
Check the return value of system() when invoking CPP in the BPF parser and bail out in case of an error. This fixes the following compiler warning: bpf_parser.y:754:9: warning: ignoring return value of ‘system’, declared with attribute warn_unused_result [-Wunused-result] Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'flowtop/.gitignore')
0 files changed, 0 insertions, 0 deletions
rotected 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/apparmor/procattr.c')