tdb2: suppress tdb1 backend logging when locking returns EINTR or EAGAIN
authorRusty Russell <rusty@rustcorp.com.au>
Wed, 31 Aug 2011 05:55:16 +0000 (15:25 +0930)
committerRusty Russell <rusty@rustcorp.com.au>
Wed, 31 Aug 2011 05:55:16 +0000 (15:25 +0930)
commita391b2b900bc6d5c0467869a454bdb5c51b5a3be
tree8defad3827a126848086f56a93c9984d47410b22
parentfbad02b680b6cbc33ae305ae1cbcdead4eedc7b1
tdb2: suppress tdb1 backend logging when locking returns EINTR or EAGAIN

The TDB1 code logs multiple times on errors; we must prevent that in
the limited case where locking fails.  With TDB2, this can happen due
to the lock function attribute, where the user supplies replacement
locking functions which are allowed to return with errno EAGAIN or
EINTR for various special-effects.  Flooding the logs for this is
unfriendly.
ccan/tdb2/tdb1_lock.c
ccan/tdb2/tdb1_transaction.c