linux-kernel - Re: [PATCH v3 1/8] atomics: add acquire/release/relaxed variants of some atomic operations

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 27 Jul 2015 19:51:39 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Will Deacon <will.deacon@....com>
Cc:	"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
	"Waiman.Long@...com" <Waiman.Long@...com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"paulmck@...ux.vnet.ibm.com" <paulmck@...ux.vnet.ibm.com>
Subject: Re: [PATCH v3 1/8] atomics: add acquire/release/relaxed variants of
 some atomic operations

On Mon, Jul 27, 2015 at 05:33:00PM +0100, Will Deacon wrote:
> Something like below?
> 
> Will
> 
> --->8
> 
> diff --git a/include/linux/atomic.h b/include/linux/atomic.h
> index 899b4035569e..d2515c05e7c8 100644
> --- a/include/linux/atomic.h
> +++ b/include/linux/atomic.h
> @@ -14,6 +14,11 @@
>   * - Release: Provides RELEASE semantics, _release suffix.
>   * - Relaxed: No ordering guarantees, _relaxed suffix.
>   *
> + * For compound atomics performing both a load and a store, ACQUIRE
> + * semantics apply only to the load and RELEASE semantics only to the
> + * store portion of the operation. Note that a failed cmpxchg_acquire
> + * does -not- imply any memory ordering constraints.
> + *
>   * See Documentation/memory-barriers.txt for ACQUIRE/RELEASE definitions.
>   */

Yep, works for me.
--
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/