Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp1191354pxx; Tue, 27 Oct 2020 10:18:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwSnfgQTVvgXmQreLc81hURsv6dBW+ayoXs4vgm6k9VRBmLzSwJNVlkd4zLwJnnmyksIPnU X-Received: by 2002:a17:906:cd13:: with SMTP id oz19mr3368683ejb.455.1603819098471; Tue, 27 Oct 2020 10:18:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603819098; cv=none; d=google.com; s=arc-20160816; b=fOYXqwBR8ERpUCbPpzBv/q8fGBOUqJpF1VOv+WJq4XNfCKaX0xAxwg3rLjTe7yReHw lXtWcekLj/PeedllBVU9LFuBmopHFwpT/1P8IQ6c8+i8XxhDubX6mR1ljGZdIHae91Rt 295gpb5l9PHfDgnc2hN0bBxcKczxQ8FfLFquZ0hBSfeArZDJl937MCpXVBNlijeHHbXV N2HAblTFSRSRXYG8Qh/kZp/Zmiu8+kTp6SFteW77OFdL6z/r+PIbuiLu85u1cSQvEyGP VrwZyyn6lJvtjHhySPl5RDTojJ/IL0ca5tUWPlhJ00mUJ4Ke5m84DAEvhE6//ejetjXd lw8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:message-id:date:to:cc:from:subject :references:in-reply-to:content-transfer-encoding:mime-version; bh=IZf0WVSwYVr4Zl0WWmWd7FCts84nnw4qLIhgXIpQE+Q=; b=fjeL777dNzatQjspp/65yy8c/+MMkAIwF+orkwkCd0154mSvGXI/ZqrVJ7j3uiknby mRW7ZPqKSZGBRR3mMo1KeM1wKvAukHHLvYG4vnc8KMmQr9f0pGXrSEbGBxc6M8bShqn+ kRjaQsIql4VKuT5GiJZ6Bmc0brsUnQwkXnATCeyShC2aNIra7fxd9DOcHIZLwk2AM6bn 9H+pc7KVOwCUawv71/KWoWacBpRcgVmN6b/u+EZ+ojuQS6DndN+r8I9/vDN3OhckAmyT AA31KDHvD21OwYmx2wb5I+WLHwfoPp/j3MO9XzxOZxfgguh2x1C68DGCnmu6MdcLxdWV IqRw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e16si1471517ejz.457.2020.10.27.10.17.55; Tue, 27 Oct 2020 10:18:18 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1811164AbgJ0Qhp convert rfc822-to-8bit (ORCPT + 99 others); Tue, 27 Oct 2020 12:37:45 -0400 Received: from mail.fireflyinternet.com ([77.68.26.236]:58585 "EHLO fireflyinternet.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1810239AbgJ0QfO (ORCPT ); Tue, 27 Oct 2020 12:35:14 -0400 X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=78.156.65.138; Received: from localhost (unverified [78.156.65.138]) by fireflyinternet.com (Firefly Internet (M1)) with ESMTP (TLS) id 22819579-1500050 for multiple; Tue, 27 Oct 2020 16:34:57 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT In-Reply-To: <20201027154533.GB2611@hirez.programming.kicks-ass.net> References: <20200930094937.GE2651@hirez.programming.kicks-ass.net> <160208761332.7002.17400661713288945222.tip-bot2@tip-bot2> <160379817513.29534.880306651053124370@build.alporthouse.com> <20201027115955.GA2611@hirez.programming.kicks-ass.net> <20201027123056.GE2651@hirez.programming.kicks-ass.net> <160380535006.10461.1259632375207276085@build.alporthouse.com> <20201027154533.GB2611@hirez.programming.kicks-ass.net> Subject: Re: [tip: locking/core] lockdep: Fix usage_traceoverflow From: Chris Wilson Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org, tip-bot2 for Peter Zijlstra , Qian Cai , x86 To: Peter Zijlstra Date: Tue, 27 Oct 2020 16:34:53 +0000 Message-ID: <160381649396.10461.15013696719989662769@build.alporthouse.com> User-Agent: alot/0.9 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Peter Zijlstra (2020-10-27 15:45:33) > On Tue, Oct 27, 2020 at 01:29:10PM +0000, Chris Wilson wrote: > > > <4> [304.908891] hm#2, depth: 6 [6], 3425cfea6ff31f7f != 547d92e9ec2ab9af > > <4> [304.908897] WARNING: CPU: 0 PID: 5658 at kernel/locking/lockdep.c:3679 check_chain_key+0x1a4/0x1f0 > > Urgh, I don't think I've _ever_ seen that warning trigger. > > The comments that go with it suggest memory corruption is the most > likely trigger of it. Is it easy to trigger? For the automated CI, yes, the few machines that run that particular HW test seem to hit it regularly. I have not yet reproduced it for myself. I thought it looked like something kasan would provide some insight for and we should get a kasan run through CI over the w/e. I suspect we've feed in some garbage and called it a lock. -Chris