Displaying 8 results from an estimated 8 matches for "next_stack".
2017 Jun 27
0
[PATCH v3 3/5] threads: Use thread-local storage for errors.
...error_data->error_cb_stack->error_cb_data = error_data->error_cb_data;
guestfs_set_error_handler (g, cb, data);
}
@@ -267,26 +402,21 @@ void
guestfs_pop_error_handler (guestfs_h *g)
{
ACQUIRE_LOCK_FOR_CURRENT_SCOPE (g);
+ struct error_data *error_data;
struct error_cb_stack *next_stack;
- if (g->error_cb_stack) {
- next_stack = g->error_cb_stack->next;
- guestfs_set_error_handler (g, g->error_cb_stack->error_cb,
- g->error_cb_stack->error_cb_data);
- free (g->error_cb_stack);
- g->error_cb_stack = next_stack;...
2015 Jun 06
0
[PATCH 3/5] threads: Use thread-local storage for errors.
...or_data->error_cb_stack->error_cb_data = error_data->error_cb_data;
guestfs_set_error_handler (g, cb, data);
@@ -258,32 +393,27 @@ guestfs_push_error_handler (guestfs_h *g,
void
guestfs_pop_error_handler (guestfs_h *g)
{
+ struct error_data *error_data;
struct error_cb_stack *next_stack;
ACQUIRE_LOCK (g);
- if (g->error_cb_stack) {
- next_stack = g->error_cb_stack->next;
- guestfs_set_error_handler (g, g->error_cb_stack->error_cb,
- g->error_cb_stack->error_cb_data);
- free (g->error_cb_stack);
- g->error...
2015 Jun 16
5
[PATCH threads v2 0/5] Add support for thread-safe handle.
Previous discussion here:
https://www.redhat.com/archives/libguestfs/2015-June/thread.html#00048
v2:
- Use a cleanup handler to release the lock.
- Rebase to upstream.
Note I have not fixed the problem(s) with error handling (patch 3).
2015 Jun 06
7
[PATCH 0/5] Add support for thread-safe handle.
This patch isn't ready to go upstream. In fact, I think we might do a
quick 1.30 release soon, and save this patch, and also the extensive
changes proposed for the test suite[1], to after 1.30.
Currently it is not safe to use the same handle from multiple threads,
unless you implement your own mutexes. See:
http://libguestfs.org/guestfs.3.html#multiple-handles-and-multiple-threads
These
2017 Jun 27
9
[PATCH v3 0/5] threads: Add support for thread-safe handle.
Previously posted in 2015:
v1: https://www.redhat.com/archives/libguestfs/2015-June/msg00048.html
v2: https://www.redhat.com/archives/libguestfs/2015-June/msg00118.html
I have rebased and tidied up the patches, fixing a few spelling
mistakes, but they are broadly the same as before. I also ran all the
tests, which pass.
As with the previous versions, this makes a change to the API, where
you
2015 Jun 06
0
[PATCH 2/5] threads: Acquire and release the lock around each public guestfs_* API.
...k;
@@ -201,6 +251,8 @@ guestfs_push_error_handler (guestfs_h *g,
g->error_cb_stack->error_cb_data = g->error_cb_data;
guestfs_set_error_handler (g, cb, data);
+
+ RELEASE_LOCK (g);
}
void
@@ -208,6 +260,8 @@ guestfs_pop_error_handler (guestfs_h *g)
{
struct error_cb_stack *next_stack;
+ ACQUIRE_LOCK (g);
+
if (g->error_cb_stack) {
next_stack = g->error_cb_stack->next;
guestfs_set_error_handler (g, g->error_cb_stack->error_cb,
@@ -217,6 +271,8 @@ guestfs_pop_error_handler (guestfs_h *g)
}
else
guestfs_int_init_error_handler (g);
+
+ REL...
2017 Jul 21
6
[PATCH v3 REPOST 0/5] threads: Add support for thread-safe handle.
Previously posted in 2015:
v1: https://www.redhat.com/archives/libguestfs/2015-June/msg00048.html
v2: https://www.redhat.com/archives/libguestfs/2015-June/msg00118.html
This series was posted about 4 weeks ago:
v3: https://www.redhat.com/archives/libguestfs/2017-June/msg00287.html
There is no change in this series except I rebased it against current
upstream head and retested. Last time there
2015 Feb 14
2
[PATCH 0/2] Change guestfs__*
libguestfs has used double and triple underscores in identifiers.
These aren't valid for global names in C++.
(http://stackoverflow.com/a/228797)
These large but completely mechanical patches change the illegal
identifiers to legal ones.
Rich.