xfrm: Add a dummy network device for napi. - net-next.git - net-next plumbings

summary refs log tree commit diff

path: root/sound/pci/ymfpci

diff options

author	Steffen Klassert <steffen.klassert@secunet.com>	2017-01-30 06:45:43 +0100
committer	Steffen Klassert <steffen.klassert@secunet.com>	2017-01-30 06:45:43 +0100
commit	1995876a06bcf6f9f7d7b699bdbf387831679771 (patch)
tree	9f308c68f35e233c0ce5ce91d64bb096bec9ebb7 /sound/pci/ymfpci
parent	f991bb9da142ba79b54ed0757f22e756f45e2c5a (diff)

xfrm: Add a dummy network device for napi.

This patch adds a dummy network device so that we can use gro_cells for IPsec GRO. With this, we handle IPsec GRO with no impact on the generic networking code. Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

Diffstat (limited to 'sound/pci/ymfpci')

0 files changed, 0 insertions, 0 deletions

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 'sound/pci/rme9652/hdspm.c')