i40e/i40evf : Changed version from 1.6.25 to 1.6.27 - net-next.git

diff options

author	Bimmy Pujari <bimmy.pujari@intel.com>	2016-11-28 16:06:11 -0800
committer	Jeff Kirsher <jeffrey.t.kirsher@intel.com>	2017-02-11 20:39:01 -0800
commit	cfffef76e7fa5b9ac3ec8298336d0265bc86af3c (patch)
tree	116526604aa490bb4b5e7dd660d10a9fd861d803 /tools/time
parent	a158aeaf5bb5b014240b360693751476aca7440b (diff)

i40e/i40evf : Changed version from 1.6.25 to 1.6.27

Signed-off-by: Bimmy Pujari <bimmy.pujari@intel.com> Tested-by: Andrew Bowers <andrewx.bowers@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>

Diffstat (limited to 'tools/time')

0 files changed, 0 insertions, 0 deletions

30_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>

Diffstat (limited to 'net/wireless/wext-spy.c')


context:
space:
mode: