tdb2: fix bogus error from tdb_unlockall() after fork in tdb1 backend.
authorRusty Russell <rusty@rustcorp.com.au>
Tue, 13 Sep 2011 22:43:13 +0000 (08:13 +0930)
committerRusty Russell <rusty@rustcorp.com.au>
Tue, 13 Sep 2011 22:43:13 +0000 (08:13 +0930)
commit6b11a2630123453a7f40f728641882c440b57010
tree028c4379cae21c8d00e1de170fe8307879f78af6
parentd26908846a84bcff7860ebdb384bbff030206675
tdb2: fix bogus error from tdb_unlockall() after fork in tdb1 backend.

We're always allowed to unlock after a fork; by setting the count to 0
before calling the generic unlock function we don't trigger the pid
check.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
(Imported from CCAN commit ba5bb8eae6bcd230fd5321c618d6a9d56e74e7d1)
lib/tdb2/tdb1_lock.c