From: Stephan Mueller <smueller@chronox.de>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will.deacon@arm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"Theodore Ts'o" <tytso@mit.edu>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
mancha security <mancha1@zoho.com>,
Mark Charlebois <charlebm@gmail.com>,
Behan Webster <behanw@converseincode.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: interesting commit about llvm introducing barrier_data()
Date: Tue, 23 Feb 2016 15:46:19 +0100 [thread overview]
Message-ID: <1605703.GSn7kbzMda@tauon.atsec.com> (raw)
In-Reply-To: <675593567.5328.1456237963352.JavaMail.zimbra@efficios.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
Am Dienstag, 23. Februar 2016, 14:32:43 schrieb Mathieu Desnoyers:
Hi Mathieu,
> ----- On Feb 23, 2016, at 9:23 AM, Paul E. McKenney
paulmck@linux.vnet.ibm.com wrote:
> > On Tue, Feb 23, 2016 at 02:02:26PM +0000, Mathieu Desnoyers wrote:
> >> commit 7829fb09a2b4268b30dd9bc782fa5ebee278b137
> >> Author: Daniel Borkmann <daniel@iogearbox.net>
> >> Date: Thu Apr 30 04:13:52 2015 +0200
> >>
> >> lib: make memzero_explicit more robust against dead store elimination
> >>
> >> ^ interesting commit. Any idea on the impact of this on kernel RCU
> >> implementation and liburcu cmm_barrier() ?
> >
> > First I knew of it! But I bet that more like this are needed. ;-)
>
> I recommend you check my IRC discussion with peterz on the matter of
> this new "barrier_data()".
>
The key idea of the memzero_explicit is about forcing the compiler to do a
memset.
See the trivial test attached.
Ciao
Stephan
[-- Attachment #2: memset_secure.c.xz --]
[-- Type: application/x-xz, Size: 1708 bytes --]
next prev parent reply other threads:[~2016-02-23 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1168693945.5302.1456236146207.JavaMail.zimbra@efficios.com>
[not found] ` <20160223142336.GK3522@linux.vnet.ibm.com>
2016-02-23 14:32 ` interesting commit about llvm introducing barrier_data() Mathieu Desnoyers
2016-02-23 14:46 ` Stephan Mueller [this message]
2016-02-23 14:58 ` Mathieu Desnoyers
2016-02-23 16:10 ` Paul E. McKenney
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=1605703.GSn7kbzMda@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=behanw@converseincode.com \
--cc=charlebm@gmail.com \
--cc=daniel@iogearbox.net \
--cc=hannes@stressinduktion.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mancha1@zoho.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=will.deacon@arm.com \
/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