Displaying 3 results from an estimated 3 matches for "list_freed".
2020 Sep 07
0
[libnbd PATCH 2/2] generator: Free closures on failure
...XIT_SUCCESS);
}
diff --git a/tests/newstyle-limited.c b/tests/newstyle-limited.c
index fd89620..4479a14 100644
--- a/tests/newstyle-limited.c
+++ b/tests/newstyle-limited.c
@@ -84,6 +84,17 @@ list_cb (void *opaque, const char *name, const char *description)
exit (EXIT_FAILURE);
}
+static bool list_freed = false;
+static void
+free_list_cb (void *opaque)
+{
+ if (list_freed) {
+ fprintf (stderr, "%s: list callback mistakenly freed twice", progname);
+ exit (EXIT_FAILURE);
+ }
+ list_freed = true;
+}
+
int
main (int argc, char *argv[])
{
@@ -144,10 +155,15 @@ main (int argc, ch...
2020 Sep 07
4
[libnbd PATCH 0/2] Fix memory leak with closures
As promised in my earlier thread on libnbd completion callback question.
Eric Blake (2):
generator: Refactor handling of closures in unlocked functions
generator: Free closures on failure
docs/libnbd.pod | 2 +-
generator/C.ml | 48 +++++++++++------
generator/C.mli | 1 +
lib/debug.c | 7 +--
lib/opt.c | 31 ++++++-----
2023 Jul 13
2
[libnbd PATCH 0/2] Fix docs and testing of completion callback
This is my proposal for fixing the documentation to match practice
(namely, that completion.callback is not invoked in the cases where
the aio call itself reports errors); we could instead try to go the
other direction and tweak the generator to guarantee that both
completion.callback and completion.free are reached no matter what,
but that felt more invasive to me.
Eric Blake (2):
api: Tighten