[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-exchange] branch master updated: -document why re-locking here is
From: |
gnunet |
Subject: |
[taler-exchange] branch master updated: -document why re-locking here is safe -- at least right now |
Date: |
Sat, 22 Oct 2022 00:27:35 +0200 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a commit to branch master
in repository exchange.
The following commit(s) were added to refs/heads/master by this push:
new 4524180a -document why re-locking here is safe -- at least right now
4524180a is described below
commit 4524180ada7d49e2f3ea4356df4706f2c9b0841d
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sat Oct 22 00:27:32 2022 +0200
-document why re-locking here is safe -- at least right now
---
src/bank-lib/fakebank.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/src/bank-lib/fakebank.c b/src/bank-lib/fakebank.c
index fa1475b7..34b87be5 100644
--- a/src/bank-lib/fakebank.c
+++ b/src/bank-lib/fakebank.c
@@ -3630,6 +3630,10 @@ access_withdrawals_confirm (struct TALER_FAKEBANK_Handle
*h,
TALER_EC_BANK_DUPLICATE_RESERVE_PUB_SUBJECT,
NULL);
}
+ /* Re-acquiring the lock and continuing to operate on 'wo'
+ is currently (!) acceptable because we NEVER free 'wo'
+ until shutdown. We may want to revise this if keeping
+ all withdraw operations in RAM becomes an issue... */
GNUNET_assert (0 ==
pthread_mutex_lock (&h->big_lock));
wo->confirmation_done = true;
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-exchange] branch master updated: -document why re-locking here is safe -- at least right now,
gnunet <=