linux-kernel - Re: [PATCH v4 tip/core/locking 0/4] Memory-barrier documentation updates

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131205122851.GB20562@gmail.com>
Date:	Thu, 5 Dec 2013 13:28:51 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Henrik Austad <henrik@...tad.us>
Cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org, laijs@...fujitsu.com,
	dipankar@...ibm.com, akpm@...ux-foundation.org,
	mathieu.desnoyers@...icios.com, josh@...htriplett.org,
	niv@...ibm.com, tglx@...utronix.de, peterz@...radead.org,
	rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com,
	darren@...art.com, fweisbec@...il.com, sbw@....edu
Subject: Re: [PATCH v4 tip/core/locking 0/4] Memory-barrier documentation
 updates


* Henrik Austad <henrik@...tad.us> wrote:

> On Wed, Dec 04, 2013 at 02:46:28PM -0800, Paul E. McKenney wrote:
> > Hello!
> 
> Hi Paul,
> 
> > This series applies some long-needed updates to memory-barriers.txt:
> > 
> > 1.	Add ACCESS_ONCE() calls where needed to ensure their inclusion
> > 	in code copy-and-pasted from this file.
> > 
> > 2.	Add long atomic examples alongside the existing atomics.
> > 
> > 3.	Prohibit architectures supporting the Linux kernel from
> > 	speculating stores.
> 
> Just me, or is the 3rd patch missing from lkml?

It had a Cc: list from hell so vger probably rejected it as spam.

Thanks,

	Ingo
--
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/