[tip:locking/core] locking/lockdep: Revert qrwlock recusive stuff

2014-10-02 Thread tip-bot for Peter Zijlstra
Commit-ID: 8acd91e8620836a56ff62028ed28ba629f2881a0 Gitweb: http://git.kernel.org/tip/8acd91e8620836a56ff62028ed28ba629f2881a0 Author: Peter Zijlstra AuthorDate: Tue, 30 Sep 2014 15:26:00 +0200 Committer: Ingo Molnar CommitDate: Fri, 3 Oct 2014 06:09:30 +0200 locking/lockdep: Revert

Re: locking/lockdep: Revert qrwlock recusive stuff

2014-09-30 Thread Borislav Petkov
On Tue, Sep 30, 2014 at 03:26:00PM +0200, Peter Zijlstra wrote: > > Now with locking self test reverted too and extra changelog. > > > --- > Subject: locking/lockdep: Revert qrwlock recusive stuff > From: Peter Zijlstra > Date: Tue, 30 Sep 2014 14:48:07 +0200 > >

Re: locking/lockdep: Revert qrwlock recusive stuff

2014-09-30 Thread Peter Zijlstra
Now with locking self test reverted too and extra changelog. --- Subject: locking/lockdep: Revert qrwlock recusive stuff From: Peter Zijlstra Date: Tue, 30 Sep 2014 14:48:07 +0200 Commit f0bab73cb539 ("locking/lockdep: Restrict the use of recursive read_lock() with qrwlock") chang

locking/lockdep: Revert qrwlock recusive stuff

2014-09-30 Thread Peter Zijlstra
Commit f0bab73cb539 ("locking/lockdep: Restrict the use of recursive read_lock() with qrwlock") changed lockdep to try and conform to the qrwlock semantics which differ from the traditional rwlock semantics. In particular qrwlock is fair outside of interrupt context, but in interrupt context read