[opendnssec/opendnssec] 8aa2f4: Make schedule lock recursive

Yuri Schaeffer yuri at nlnetlabs.nl
Sat Aug 6 22:40:06 CEST 2016


  Branch: refs/heads/develop
  Home:   https://github.com/opendnssec/opendnssec
  Commit: 8aa2f4b9249125c22a3db2b3fb0164c09f082c93
      https://github.com/opendnssec/opendnssec/commit/8aa2f4b9249125c22a3db2b3fb0164c09f082c93
  Author: Yuri Schaeffer <yuri at nlnetlabs.nl>
  Date:   2016-08-06 (Sat, 06 Aug 2016)

  Changed paths:
    M enforcer/src/scheduler/schedule.c

  Log Message:
  -----------
  Make schedule lock recursive

The reason we allow recursive locks is because we broadcast
a condition in an ISR. The main thread would receive this
interrupt. If we would do no locking in the ISR we risk missing
conditions. If we use a normal mutex we risk a deadlock if the
main thread occasionally grabs the lock.


  Commit: b5bd1590f4d1cc162d1c94461e1ef6057c1c40ec
      https://github.com/opendnssec/opendnssec/commit/b5bd1590f4d1cc162d1c94461e1ef6057c1c40ec
  Author: Yuri Schaeffer <yuri at nlnetlabs.nl>
  Date:   2016-08-06 (Sat, 06 Aug 2016)

  Changed paths:
    M enforcer/src/scheduler/schedule.c

  Log Message:
  -----------
  Merge pull request #497 from yschaeff/next_change

Make schedule lock recursive


Compare: https://github.com/opendnssec/opendnssec/compare/088678138739...b5bd1590f4d1


More information about the Opendnssec-commits mailing list