Displaying 6 results from an estimated 6 matches for "cleanup_gl_recursive_lock_unlock".
2017 Nov 18
2
Re: [nbdkit PATCH 3/6] connections: Add read/write lock over client I/O
...for doing so is
> larger, because it requires adding to new sub-function {} scopes and
> reindenting (we have two different locks in play here).
>
Interestingly, it doesn't compile if you lack attribute((cleanup)).
Libguestfs has:
common/utils/cleanups.h:/* XXX no safe equivalent to
CLEANUP_GL_RECURSIVE_LOCK_UNLOCK */
and will fail to compile if the compiler lacks the attribute - arguably,
since no one has reported that compilation failure, it seems no one
cares about libguestfs that is not also in possession of modern gcc or
clang. And we already have a configure-time check whether
attribute((cleanup)) is...
2017 Nov 18
0
Re: [nbdkit PATCH 3/6] connections: Add read/write lock over client I/O
...it requires adding to new sub-function {} scopes and
>> reindenting (we have two different locks in play here).
>>
>
> Interestingly, it doesn't compile if you lack attribute((cleanup)).
> Libguestfs has:
>
> common/utils/cleanups.h:/* XXX no safe equivalent to
> CLEANUP_GL_RECURSIVE_LOCK_UNLOCK */
>
> and will fail to compile if the compiler lacks the attribute - arguably,
> since no one has reported that compilation failure, it seems no one
> cares about libguestfs that is not also in possession of modern gcc or
> clang. And we already have a configure-time check whether...
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).
2017 Nov 17
2
Re: [nbdkit PATCH 3/6] connections: Add read/write lock over client I/O
On Thu, Nov 16, 2017 at 09:26:54PM -0600, Eric Blake wrote:
> In preparation for parallel processing, we need to be sure that
> two threads belonging to the same connection cannot interleave
> their I/O except at message boundaries. Add a mutex around
> all reads and writes that must occur as a group (for now, there
> is no contention for either mutex).
>
> Signed-off-by:
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
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