Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp5888516ybn; Sun, 29 Sep 2019 07:50:49 -0700 (PDT) X-Google-Smtp-Source: APXvYqz3KAMB6d2dN7m6Z90YINN6b5FgTO6NJwZ+VZ3srRGGkhkjE6nxLfqJhl6K9gRk+gJ4qylQ X-Received: by 2002:a17:906:d97a:: with SMTP id rp26mr15865255ejb.251.1569768649366; Sun, 29 Sep 2019 07:50:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569768649; cv=none; d=google.com; s=arc-20160816; b=znt6gWykKtaWZOnPvZptXLDIqjwVZKeJcl1H5NvU+kQvLnmEgxdK/3Ip6MGMlXWEju uOVzmC948/5pRmiovBicJ9dQe/blzK9iRQK4SzQ7qYaUPn65jGUB8qQEDCXIbTArHxFu pkoHLVxaJb2QxsGi1ui/lmm5LLdK8Wy6m4c/dB+VCALIZBJqkW0IwDfBbZ5AGa1LAzKv KCsY0NLtyE0DTX6KNJuQLjwEcW+nQyu3FueiIJFtHylsXuYv6nQ+eKGZzk496Fa35n+4 YmVAbsUYXNXj7FRx6plTG40vN4H2KfCCcM9AAbgpMM1faOIvpir9knotAgleiDWRrWqi P2Gg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=YOO/pxMQ5q8qByanP3BAC/m8ivWyN4cB59RAFGQj6Ww=; b=cCCLdGFDGB4QrAwOflX4WjNCHR0/GN/nNytINffTUB5U+f6A4q5Zy2EpRWTUiEeXDZ JIPvjgxYRRBtU6s8el+6zTdGeyK1Y/+AKUbUi/zEh+vsmGPIsr9wrJS87MXA9vVXM+PB 6ufLngy5bwcyPRaUNLi0gsOherWkGbj2BlSzgw4hn/U7b7KGRe+QtmZCLY+C5db42xIE bJsCoWiu1p+kONV/sPXvooImcvutPOPZDsZMBHrMs9Tlkqf0Xa50n7gmFtbJ/a2sLgOo nZxlS2QWjAXo6jHv5MDSZhxLuaeYjzWGlUqf7tu0ZnlaHdFhggPEqzHnPK4sDEwksKik aTng== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z7si5598016ejr.99.2019.09.29.07.49.55; Sun, 29 Sep 2019 07:50:49 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728576AbfI2Oo1 (ORCPT + 99 others); Sun, 29 Sep 2019 10:44:27 -0400 Received: from www262.sakura.ne.jp ([202.181.97.72]:59224 "EHLO www262.sakura.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725948AbfI2Oo1 (ORCPT ); Sun, 29 Sep 2019 10:44:27 -0400 Received: from fsav402.sakura.ne.jp (fsav402.sakura.ne.jp [133.242.250.101]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id x8TEhfp4094706; Sun, 29 Sep 2019 23:43:41 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav402.sakura.ne.jp (F-Secure/fsigk_smtp/530/fsav402.sakura.ne.jp); Sun, 29 Sep 2019 23:43:41 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/530/fsav402.sakura.ne.jp) Received: from [192.168.1.8] (softbank126227201116.bbtec.net [126.227.201.116]) (authenticated bits=0) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTPSA id x8TEhd7U094685 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NO); Sun, 29 Sep 2019 23:43:40 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Subject: Re: [PATCH 4.19 36/63] locking/lockdep: Add debug_locks check in __lock_downgrade() To: Greg Kroah-Hartman , linux-kernel@vger.kernel.org Cc: stable@vger.kernel.org, syzbot+53383ae265fb161ef488@syzkaller.appspotmail.com, Waiman Long , "Peter Zijlstra (Intel)" , Andrew Morton , Linus Torvalds , "Paul E. McKenney" , Thomas Gleixner , Will Deacon , Ingo Molnar , Sasha Levin References: <20190929135031.382429403@linuxfoundation.org> <20190929135038.482721804@linuxfoundation.org> From: Tetsuo Handa Message-ID: <801c81d2-ce72-8eb3-a18b-1b0943270fc4@i-love.sakura.ne.jp> Date: Sun, 29 Sep 2019 23:43:38 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20190929135038.482721804@linuxfoundation.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/09/29 22:54, Greg Kroah-Hartman wrote: > From: Waiman Long > > [ Upstream commit 513e1073d52e55b8024b4f238a48de7587c64ccf ] > > Tetsuo Handa had reported he saw an incorrect "downgrading a read lock" > warning right after a previous lockdep warning. It is likely that the > previous warning turned off lock debugging causing the lockdep to have > inconsistency states leading to the lock downgrade warning. > > Fix that by add a check for debug_locks at the beginning of > __lock_downgrade(). Please drop "[PATCH 4.19 36/63] locking/lockdep: Add debug_locks check in __lock_downgrade()". We had a revert patch shown below in the past. "[PATCH 4.19 37/63] locking/lockdep: Add debug_locks check in __lock_downgrade() - again" seems the correct patch. On 2019/04/25 17:08, gregkh@linuxfoundation.org wrote:> > This is a note to let you know that I've just added the patch titled > > Revert "locking/lockdep: Add debug_locks check in __lock_downgrade()" > > to the 4.19-stable tree which can be found at: > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary > > The filename of the patch is: > revert-locking-lockdep-add-debug_locks-check-in-__lock_downgrade.patch > and it can be found in the queue-4.19 subdirectory. > > If you, or anyone else, feels it should not be added to the stable tree, > please let know about it. > > >>From 7f437eec35a20f40d9ff82ae1c072b211c29e8e0 Mon Sep 17 00:00:00 2001 > From: Greg Kroah-Hartman > Date: Thu, 25 Apr 2019 10:00:43 +0200 > Subject: Revert "locking/lockdep: Add debug_locks check in __lock_downgrade()" > > From: Greg Kroah-Hartman > > This reverts commit 0e0f7b30721233ce610bde2395a8e58ff7771475 which was > commit 71492580571467fb7177aade19c18ce7486267f5 upstream. > > Tetsuo rightly points out that the backport here is incorrect, as it > touches the __lock_set_class function instead of the intended > __lock_downgrade function. > > Reported-by: Tetsuo Handa > Cc: Waiman Long > Cc: Peter Zijlstra (Intel) > Cc: Andrew Morton > Cc: Linus Torvalds > Cc: Paul E. McKenney > Cc: Peter Zijlstra > Cc: Thomas Gleixner > Cc: Will Deacon > Cc: Ingo Molnar > Cc: Sasha Levin > Signed-off-by: Greg Kroah-Hartman > --- > kernel/locking/lockdep.c | 3 --- > 1 file changed, 3 deletions(-) > > --- a/kernel/locking/lockdep.c > +++ b/kernel/locking/lockdep.c > @@ -3567,9 +3567,6 @@ __lock_set_class(struct lockdep_map *loc > unsigned int depth; > int i; > > - if (unlikely(!debug_locks)) > - return 0; > - > depth = curr->lockdep_depth; > /* > * This function is about (re)setting the class of a held lock, > >