[RELEASE] Userspace RCU 0.7.15 and 0.8.8

[Mathieu Desnoyers]

Hi,

liburcu is a LGPLv2.1 userspace RCU (read-copy-update) library. This
data synchronization library provides read-side access which scales
linearly with the number of cores. It does so by allowing multiple
copies of a given data structure to live at the same time, and by
monitoring the data structure accesses to detect grace periods after
which memory reclamation is possible.

liburcu-cds provides efficient data structures based on RCU and
lock-free algorithms. Those structures include hash tables, queues,
stacks, and doubly-linked lists.

Those are bugfix releases for stable-0.7 and stable-0.8 branches.
Small fixes to the tests (volatile in assert() and out of tree test
fix) were not backported to stable-0.7 due to important changes
to the test tree layout between 0.7 and 0.8.

Changelog:
2015-09-09 Userspace RCU 0.7.15
        * Disable sys_membarrier
        * uatomic: Specify complete types for atomic function calls
        * Fix: handle sys_futex() FUTEX_WAIT interrupted by signal
        * Fix: compat_futex.c: *uaddr should be read as volatile
        * Fix: call_rcu_thread() affinity failure
        * urcu: fix deprecation warning with new glibc

2015-09-09 Userspace RCU 0.8.8
        * Disable sys_membarrier
        * Fix: volatile in assert()
        * uatomic: Specify complete types for atomic function calls
        * Fix: handle sys_futex() FUTEX_WAIT interrupted by signal
        * Fix: compat_futex.c: *uaddr should be read as volatile
        * Fix: make benchmark test run in oot build
        * Fix: call_rcu_thread() affinity failure
        * urcu: fix deprecation warning with new glibc

Project website: http://liburcu.org
Git repository: git://git.liburcu.org/urcu.git

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/