linux-kernel - Re: [GIT PULL v2 rcu/next] memory-barriers.txt commits for 4.6

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: <20160316072625.GA10500@gmail.com>
Date:	Wed, 16 Mar 2016 08:26:25 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, sj38.park@...il.com,
	josh@...htriplett.org, rostedt@...dmis.org,
	mathieu.desnoyers@...icios.com, jiangshanlai@...il.com,
	torvalds@...ux-foundation.org
Subject: Re: [GIT PULL v2 rcu/next] memory-barriers.txt commits for 4.6


* Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:

> [...] In fact, in view of the no-diagrams and no-quizzes restrictions, I don't 
> see a way to improve on comments in the source code. [...]

So I don't think there's such a hard restriction: AFAICS Linus's main problem was 
the dual .html and .htmlx file for what essentially are the same documents.

If you can solve that with a single (.html?) file then I think it's all OK.

> The memory-barriers.txt commits are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo
> 
> for you to fetch changes up to 65f95ff2e41a32dd190cf28e3abb029625eef968:
> 
>   documentation: Clarify compiler store-fusion example (2016-03-14 15:52:19 -0700)
> 
> ----------------------------------------------------------------
> Paul E. McKenney (7):
>       documentation: Fix control dependency and identical stores
>       documentation: Fix memory-barriers.txt section references
>       documentation: Remove obsolete reference to RCU-protected indexes
>       documentation: Subsequent writes ordered by rcu_dereference()
>       documentation: Distinguish between local and global transitivity
>       documentation:  Add alternative release-acquire outcome
>       documentation: Transitivity is not cumulativity
> 
> SeongJae Park (1):
>       documentation: Clarify compiler store-fusion example
> 
>  Documentation/memory-barriers.txt | 141 +++++++++++++++++++++++++++++++-------
>  1 file changed, 116 insertions(+), 25 deletions(-)

Pulled into tip:locking/urgent, thanks a lot Paul!

	Ingo