[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20141120181145.GO7996@ZenIV.linux.org.uk>
Date: Thu, 20 Nov 2014 18:11:46 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: Will Deacon <will.deacon@....com>
Cc: Andrey Konovalov <andreyknvl@...gle.com>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Davidlohr Bueso <davidlohr@...com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Dmitry Vyukov <dvyukov@...gle.com>,
Kostya Serebryany <kcc@...gle.com>,
"ktsan@...glegroups.com" <ktsan@...glegroups.com>
Subject: Re: Potential data race in dput and __d_lookup
On Thu, Nov 20, 2014 at 05:41:01PM +0000, Will Deacon wrote:
> I think it should be fine. d_lock is #defined as d_lockref.lock, and the
> whole way the lockref works is that you can either cmpxchg the lock and the
> counter
... both by a single operation, that is.
--
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