linux-kernel - Userspace RCU API (minor changes)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100115172335.GC30678@Krystal>
Date:	Fri, 15 Jan 2010 12:23:35 -0500
From:	Mathieu Desnoyers <compudj@...stal.dyndns.org>
To:	Jon Bernard <jbernard@...ian.org>, Jan Blunck <jblunck@...e.de>,
	linux-kernel@...r.kernel.org, Pedro Alves <pedro@...esourcery.com>,
	ltt-dev@...ts.casi.polymtl.ca,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	pierre-marc.fournier@...ymtl.ca
Subject: Userspace RCU API (minor changes)

Hi,

I'd like to proceed to a minor API change in the next userspace RCU
release: moving from SIGURCU to SIGRCU for the signal name. This is part
of an effort to standardize the library prefix to "rcu_".  I plan to
add support for backward compatibility, so when we see that SIGURCU is
defined, then we use that value.

Also, I am planning to rename the urcu_init() constructor to rcu_init().
It should only affect the libust tracer, which need to call it
explicitly. Normal users don't have to bother with it, as it's a library
constructor.

Also, the urcu/config.h options are renamed to:

CONFIG_RCU_HAVE_FENCE
CONFIG_RCU_HAVE_FUTEX
CONFIG_RCU_SMP
CONFIG_RCU_COMPAT_ARCH
(moving from URCU -> RCU)

So an updated system installation will keep everything in sync.

I also plan to shuffle the library names a bit, but without breaking
anything. Basically, liburcu will become the "default" version, using
sys_membarrier() when available, and using liburcu-mb as a fallback.

The signal-based liburcu will be renamed from liburcu to liburcu-signal.
People previously using the signal-based "liburcu" will automatically be
moved to the "default" liburcu version.

You might want to have a look at the current git tree head to see if
everything is fine before the release. Given that I change the API
slightly, this will definitely be a 0.4.0.

Feedback is welcome,

Thanks,

Mathieu

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/