load running state after lock is acquired
authorAlin Năstac <alin.nastac@gmail.com>
Fri, 29 Apr 2016 13:00:01 +0000 (15:00 +0200)
committerJo-Philipp Wich <jo@mein.io>
Mon, 2 May 2016 17:40:42 +0000 (18:40 +0100)
commit6cccf1ba7f0c3eb34ef4a7adc6af501376bfa875
tree24fe2ca1ddbb6c97cef54d91ea89e712f4015265
parente92392db91f6eb50288f33ccf63475aa7b9babdd
load running state after lock is acquired

When running "/etc/init.d/firewall reload & fw3 -q restart", the
fw3 instance that handle the reload might try to read the running
state after firewall was stopped by the fw3 instance that does the
restarting. Since a NULL run_state will transform reload operation in
start operation, the resulted iptables chains will contain duplicate
sets of rules.
main.c