linux-kernel - Re: [PATCH tip/core/rcu 0/9] Stop using ACCESS

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]

Message-ID: <20150323113437.28f6e682@gandalf.local.home>
Date:	Mon, 23 Mar 2015 11:34:37 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...nel.org,
	laijs@...fujitsu.com, dipankar@...ibm.com,
	akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
	josh@...htriplett.org, tglx@...utronix.de, peterz@...radead.org,
	dhowells@...hat.com, edumazet@...gle.com, dvhart@...ux.intel.com,
	fweisbec@...il.com, oleg@...hat.com, bobby.prani@...il.com
Subject: Re: [PATCH tip/core/rcu 0/9] Stop using ACCESS_ONCE (for v4.2)

On Mon, 23 Mar 2015 08:25:07 -0700
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:

> > Not sure why this was 9 patches. I think this could have easily been a
> > single patch.
> 
> In order to make it easier to deal with conflicts and to move patches
> across this series as needed.  I could consolidate them later on, just
> before they are merged, if that would help.

No, just seemed odd to me. I usually do conversions in one big swoop if
it stays in a single subsystem and architecture. Splitting a conversion
by arch or subsystem makes sense. But these were all confined to
generic RCU.

But if you are sprinkling these within another series, then I guess it
does make sense.

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