Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: linux-kernel@vger.kernel.org, lttng-dev@lists.lttng.org
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Lai Jiangshan <jiangshanlai@gmail.com>
Subject: [RELEASE] Userspace RCU 0.14.2 and 0.15.6
Date: Mon, 26 Jan 2026 09:36:55 -0500	[thread overview]
Message-ID: <d08df9ca-65d5-4873-9205-8b58311c3859@efficios.com> (raw)

Hi,

This is a release announcement for liburcu 0.14.2 and 0.15.6,
respectively for the stable 0.14 and 0.15 branches.

The most relevant fix is for the 0.15 branch, where urcu-qsbr
and urcu-mb flavors were missing a barrier between store to
update the per-thread reader counter and the following relaxed
load of the futex waiting state.

* New in this release:

Changelog:

2026-01-26 Userspace RCU 0.15.6
         * urcu-mb: Add missing TSAN annotation to _urcu_mb_read_lock_update
         * lfstack: Coding style cleanup
         * urcu-qsbr: Use CMM_SEQ_CST_FENCE for _urcu_qsbr_thread_online
         * urcu-mb: Use CMM_SEQ_CST_FENCE for _urcu_mb_read_lock_update
         * urcu-qsbr: Use CMM_SEQ_CST_FENCE for quiescent state update and offline
         * urcu-mb: Use CMM_SEQ_CST_FENCE for _urcu_mb_read_unlock_update_and_wakeup
         * Fix: Only include linux/time_types.h when __NR_futex_time64 is defined
         * Use __NR_futex_time64 in futex syscall wrapper

2026-01-26 Userspace RCU 0.14.2
         * Fix: Only include linux/time_types.h when __NR_futex_time64 is defined
         * Use __NR_futex_time64 in futex syscall wrapper
         * Cleanup: Remove useless declarations from urcu-qsbr
         * src/urcu-bp.c: assert => urcu_posix_assert

Project website: https://liburcu.org
Git repository: https://git.liburcu.org/userspace-rcu.git

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com


                 reply	other threads:[~2026-01-26 14:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d08df9ca-65d5-4873-9205-8b58311c3859@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@kernel.org \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox