From: Will Deacon <will.deacon@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: psodagud@codeaurora.org, Kees Cook <keescook@chromium.org>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Eric Biggers <ebiggers@google.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
sherryy@android.com, Vegard Nossum <vegard.nossum@oracle.com>,
Christoph Lameter <cl@linux.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Sasha Levin <alexander.levin@verizon.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Boqun Feng <boqun.feng@gmail.com>
Subject: Re: write_lock_irq(&tasklist_lock)
Date: Thu, 24 May 2018 13:49:31 +0100 [thread overview]
Message-ID: <20180524124928.GH8689@arm.com> (raw)
In-Reply-To: <CA+55aFy9mVCJUniAMVvJjqaa=ke2mx6HfkPhCGP54ncdh70peQ@mail.gmail.com>
On Wed, May 23, 2018 at 09:26:35AM -0700, Linus Torvalds wrote:
> On Wed, May 23, 2018 at 8:35 AM Will Deacon <will.deacon@arm.com> wrote:
>
> > In other words, qrwlock requires consistent locking order wrt spinlocks.
>
> I *thought* lockdep already tracked and detected this. Or is that only with
> with the sleeping versions?
There are patches in-flight to detect this:
https://marc.info/?l=linux-kernel&m=152483640529740&w=2k
as part of Boqun's work into recursive read locking.
Will
next prev parent reply other threads:[~2018-05-24 12:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 19:40 write_lock_irq(&tasklist_lock) Sodagudi Prasad
2018-05-22 20:27 ` write_lock_irq(&tasklist_lock) Linus Torvalds
2018-05-22 21:17 ` write_lock_irq(&tasklist_lock) Peter Zijlstra
2018-05-22 21:31 ` write_lock_irq(&tasklist_lock) Linus Torvalds
2018-05-23 8:19 ` write_lock_irq(&tasklist_lock) Peter Zijlstra
2018-05-23 13:05 ` write_lock_irq(&tasklist_lock) Will Deacon
2018-05-23 15:25 ` write_lock_irq(&tasklist_lock) Linus Torvalds
2018-05-23 15:36 ` write_lock_irq(&tasklist_lock) Will Deacon
2018-05-23 16:26 ` write_lock_irq(&tasklist_lock) Linus Torvalds
2018-05-24 12:49 ` Will Deacon [this message]
2018-05-24 13:51 ` write_lock_irq(&tasklist_lock) Boqun Feng
2018-05-24 17:37 ` write_lock_irq(&tasklist_lock) Sodagudi Prasad
2018-05-24 18:28 ` write_lock_irq(&tasklist_lock) Peter Zijlstra
2018-05-24 21:14 ` write_lock_irq(&tasklist_lock) Andrea Parri
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=20180524124928.GH8689@arm.com \
--to=will.deacon@arm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@verizon.com \
--cc=boqun.feng@gmail.com \
--cc=cl@linux.com \
--cc=ebiggers@google.com \
--cc=fweisbec@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=psodagud@codeaurora.org \
--cc=riel@redhat.com \
--cc=sherryy@android.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@oracle.com \
--cc=wad@chromium.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.