From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966840AbeEXMtH (ORCPT ); Thu, 24 May 2018 08:49:07 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:43954 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751041AbeEXMtE (ORCPT ); Thu, 24 May 2018 08:49:04 -0400 Date: Thu, 24 May 2018 13:49:31 +0100 From: Will Deacon To: Linus Torvalds Cc: psodagud@codeaurora.org, Kees Cook , Andy Lutomirski , Will Drewry , Andrew Morton , Rik van Riel , Thomas Gleixner , Ingo Molnar , Peter Zijlstra , Eric Biggers , Frederic Weisbecker , sherryy@android.com, Vegard Nossum , Christoph Lameter , Andrea Arcangeli , Sasha Levin , Linux Kernel Mailing List , Boqun Feng Subject: Re: write_lock_irq(&tasklist_lock) Message-ID: <20180524124928.GH8689@arm.com> References: <0879f797135033e05e8e9166a3c85628@codeaurora.org> <20180523130547.GF26965@arm.com> <20180523153607.GD2983@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 23, 2018 at 09:26:35AM -0700, Linus Torvalds wrote: > On Wed, May 23, 2018 at 8:35 AM Will Deacon 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