From: Borislav Petkov <bp@alien8.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
ego@linux.vnet.ibm.com, Waiman.Long@hp.com
Subject: Re: locking/lockdep: Revert qrwlock recusive stuff
Date: Tue, 30 Sep 2014 18:17:23 +0200 [thread overview]
Message-ID: <20140930161723.GA4473@pd.tnic> (raw)
In-Reply-To: <20140930132600.GA7444@worktop.programming.kicks-ass.net>
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 <peterz@infradead.org>
> Date: Tue, 30 Sep 2014 14:48:07 +0200
>
> 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 readers will ignore all fairness.
>
> The problem modeling this is that read and write side have different
> lock state (interrupts) semantics but we only have a single
> representation of these. Therefore lockdep will get confused, thinking
> the lock can cause interrupt lock inversions.
>
> So revert for now; the old rwlock semantics were already imperfectly
> modeled and the qrwlock extra won't fit either.
>
> If we want to properly fix this, I think we need to resurrect the work
> by Gautham did a few years ago that split the read and write state of
> locks:
>
> http://lwn.net/Articles/332801/
>
> FWIW the locking selftest that would've failed (and was reported by
> Borislav earlier) is something like:
>
> RL(X1); /* IRQ-ON */
> LOCK(A);
> UNLOCK(A);
> RU(X1);
>
> IRQ_ENTER();
> RL(X1); /* IN-IRQ */
> RU(X1);
> IRQ_EXIT();
>
> At which point it would report that because A is an IRQ-unsafe lock we
> can suffer the following inversion:
>
> CPU0 CPU1
>
> lock(A)
> lock(X1)
> lock(A)
> <IRQ>
> lock(X1)
>
> And this is 'wrong' because X1 can recurse (assuming the above lock are
> in fact read-lock) but lockdep doesn't know about this.
>
> Cc: ego@linux.vnet.ibm.com
> Cc: bp@alien8.de
Tested-by: Borislav Petkov <bp@suse.de>
Thanks!
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-09-30 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 12:48 locking/lockdep: Revert qrwlock recusive stuff Peter Zijlstra
2014-09-30 13:26 ` Peter Zijlstra
2014-09-30 16:17 ` Borislav Petkov [this message]
2014-10-03 5:29 ` [tip:locking/core] " tip-bot for Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140930161723.GA4473@pd.tnic \
--to=bp@alien8.de \
--cc=Waiman.Long@hp.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.