[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimb7bpTa0fO2VU4pSxO-a3-eQNA6zA_ikAReXsQ@mail.gmail.com>
Date: Tue, 1 Feb 2011 12:43:56 +1000
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: paulmck@...ux.vnet.ibm.com
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Peter Zijlstra <peterz@...radead.org>,
Milton Miller <miltonm@....com>, akpm@...ux-foundation.org,
Anton Blanchard <anton@...ba.org>,
xiaoguangrong@...fujitsu.com, mingo@...e.hu, jaxboe@...ionio.com,
npiggin@...il.com, rusty@...tcorp.com.au,
linux-kernel@...r.kernel.org
Subject: Re: call_function_many: fix list delete vs add race
On Tue, Feb 1, 2011 at 12:18 PM, Paul E. McKenney
<paulmck@...ux.vnet.ibm.com> wrote:
>
> Documentation/memory-barriers.txt specifies this.
Good, so it really is documented, with both cases explicitly mentioned.
That said, I do think that if your memory ordering is much weaker than
x86, you are going to see bugs that most testers don't see, and it
simply might not be worth it.
Linus
--
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/
Powered by blists - more mailing lists