netfilter: nf_tables: add check_genid to the nfnetlink subsystem - net-next.git - net-next plumbings

summary refs log tree commit diff

path: root/net/compat.c

diff options

author	Pablo Neira Ayuso <pablo@netfilter.org>	2017-02-10 12:08:20 +0100
committer	Pablo Neira Ayuso <pablo@netfilter.org>	2017-02-12 14:45:12 +0100
commit	74e8bcd21c40dbbb3d74fa904536f8a3bddafed3 (patch)
tree	a628fe0f58c4c73e877e8f33b923f99e45814641 /net/compat.c
parent	8c4d4e8b5626fec965fd5034e5bd5e57790f243f (diff)

netfilter: nf_tables: add check_genid to the nfnetlink subsystem

This patch implements the check generation id as provided by nfnetlink. This allows us to reject ruleset updates against stale baseline, so userspace can retry update with a fresh ruleset cache. Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

Diffstat (limited to 'net/compat.c')

0 files changed, 0 insertions, 0 deletions

t, `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 'include/net/ip6_route.h')