mausezahn-libs = -lcli \
-lnet \
-lpcap \
-lrt \
-lpthread \
-lm
mausezahn-objs = str.o \
staging/layer1.o \
staging/layer2.o \
staging/layer3.o \
staging/layer4.o \
staging/hextools.o \
staging/tools.o \
staging/lookupdev.o \
staging/time.o \
staging/modifications.o \
staging/send_eth.o \
staging/send.o \
staging/cdp.o \
staging/rtp.o \
staging/dns.o \
staging/rcv_rtp.o \
staging/syslog.o \
staging/cli.o \
staging/cli_cmds.o \
staging/cli_launch.o \
staging/cli_legacy.o \
staging/cli_packet.o \
staging/cli_interface.o \
staging/cli_set.o \
staging/cli_dns.o \
staging/cli_arp.o \
staging/cli_bpdu.o \
staging/cli_eth.o \
staging/cli_ip.o \
staging/cli_udp.o \
staging/cli_tcp.o \
staging/cli_rtp.o \
staging/cli_tools.o \
staging/cli_igmp.o \
staging/cli_lldp.o \
staging/cli_sequence.o \
staging/mops.o \
staging/mops_update.o \
staging/mops_tools.o \
staging/mops_checksums.o \
staging/mops_threads.o \
staging/mops_dot1Q.o \
staging/mops_mpls.o \
staging/mops_ip.o \
staging/mops_tcp.o \
staging/mops_ext.o \
staging/mops_ext_arp.o \
staging/mops_ext_bpdu.o \
staging/mops_ext_rtp.o \
staging/mopsrx_arp.o \
staging/mops_ext_igmp.o \
staging/mops_ext_lldp.o \
staging/mops_sequence.o \
staging/automops.o \
staging/parse_xml.o \
staging/tx_switch.o \
staging/llist.o \
staging/directmops.o \
staging/mausezahn.o
mausezahn-eflags = -O2 -I. -I.. \
-DVERSION_STRING=\"$(VERSION_STRING)\" \
-DVERSION_LONG=\"$(VERSION_LONG)\"
mausezahn-confs =
/a>refslogtreecommitdiff
dmaengine: pl330: fix double lock
The static bug finder EBA (http://www.iagoabal.eu/eba/) reported the
following double-lock bug:
Double lock:
1. spin_lock_irqsave(pch->lock, flags) at pl330_free_chan_resources:2236;
2. call to function `pl330_release_channel' immediately after;
3. call to function `dma_pl330_rqcb' in line 1753;
4. spin_lock_irqsave(pch->lock, flags) at dma_pl330_rqcb:1505.
I have fixed it as suggested by Marek Szyprowski.
First, I have replaced `pch->lock' with `pl330->lock' in functions
`pl330_alloc_chan_resources' and `pl330_free_chan_resources'. This avoids
the double-lock by acquiring a different lock than `dma_pl330_rqcb'.
NOTE that, as a result, `pl330_free_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>