Skip to content
Snippets Groups Projects
Select Git revision
  • 0x4A6F-rpi4
  • 0x4A6F-master
  • master
  • v2018.2.2-ffs
  • v2018.2.x default protected
  • v2016.2.4-batmanbug
  • radv-filterd
  • v2016.2.x
  • hoodselector
  • v2016.1.x
  • babel
  • v2015.1.x
  • 2014.4.x
  • 2014.3.x
  • v2018.2.2-ffs0.1
  • v2018.2.1-ffs0.1
  • v2018.2.1
  • v2018.2-ffs0.1
  • v2018.2
  • v2018.1.4
  • v2018.1.3
  • v2018.1.2
  • v2018.1.1
  • v2018.1
  • v2017.1.8
  • v2017.1.7
  • v2017.1.6
  • v2017.1.5
  • v2017.1.4
  • v2017.1.3
  • v2017.1.2
  • v2016.2.7
  • v2017.1.1
  • v2017.1
34 results

0051-ebtables-Use-flock-for-concurrent-option.patch

Blame
  • Forked from firmware / FFS Gluon
    Source project has a limited visibility.
    • Sven Eckelmann's avatar
      cb031832
      ebtables: Use flock() for --concurrent option · cb031832
      Sven Eckelmann authored
      
      The previous locking mechanism was not atomic, hence it was possible
      that a killed ebtables process would leave the lock file in place which
      in turn made future ebtables processes wait indefinitely for the lock to
      become free.
      
      Fix this by using flock(). This also simplifies code quite a bit because
      there is no need for a custom signal handler or an __exit routine
      anymore.
      
      Signed-off-by: default avatarSven Eckelmann <sven@narfation.org>
      ebtables: Use flock() for --concurrent option
      Sven Eckelmann authored
      
      The previous locking mechanism was not atomic, hence it was possible
      that a killed ebtables process would leave the lock file in place which
      in turn made future ebtables processes wait indefinitely for the lock to
      become free.
      
      Fix this by using flock(). This also simplifies code quite a bit because
      there is no need for a custom signal handler or an __exit routine
      anymore.
      
      Signed-off-by: default avatarSven Eckelmann <sven@narfation.org>