Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp403884pxx; Wed, 28 Oct 2020 07:35:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzdpzhj5wFrJohRiUNOOwncPfVzH85nKx96XjmIlWRin2h/MpKsqfGcTMojgQl57T2hH3VF X-Received: by 2002:a17:907:9604:: with SMTP id gb4mr8015935ejc.336.1603895755605; Wed, 28 Oct 2020 07:35:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603895755; cv=none; d=google.com; s=arc-20160816; b=tSaOCVdy0MoCwdMqxMuXqC/Qbnt/PjiXhhjOVPSoy3x8oy/mTAnA/J9wyj5hjwSxm/ mbv+r4J292ZX+c401ly0sIMRmBgOXuGHvaRcNX12K3b4XubbpBbiT78G+LMMkSCzankc 35D+vgLp+viaD86FByg+oRYmg+7YrlE+lwK8gqlU/IOmvR6a1Hfw0sHurSrvht/A0P6L nlMladuq9vzt1S4MQYO2ykSZkSi18W8Ejvh+mMYVBIciTlJbBNPUf2D8P634kyO1PtRC NMFxPCAiCPqScvhcwmGw8IqiZ1WgVWHfgxkWGjgDIOeTjK6cegjbk/6lQNaHrzcROq0C NGMA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=vS0WQyA1FoopoJORMaYRyN4NqXEhBztCAPdnx7wzKRQ=; b=Jb4vTWksYdVQqxjf7+4mEOSomZ+myD3epN4lkGJDCMQxYlxDHF5u+CvrGPoNAGakQ8 VCLfcbeCDuiVKF5M4qDoJghFYeWkJ88wuGeg3DCbt/woxK0eS8WLCNbyc0FXB6pUhHsu jwYpY5ZaWeqLbEE/I9VGRVmqRwyYvaArX2tPMBlUycdYvGtamOTgRq9p3Etl3HvIv4rW srYiqlUcszy5rpgpFJy66D53iy1gNJcbx3seErX0TFuhJmV872k/onZEszBHv18vM6Tp srWT54W1Z/vA/nERilTcfY7y+ciCg+TXUWQp8D+nWjTEetX5qsB7ipjTwe1Qgr9yfK3R j5dQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@infradead.org header.s=merlin.20170209 header.b=V4L7qO2R; 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 bs17si3022913ejb.543.2020.10.28.07.35.33; Wed, 28 Oct 2020 07:35:55 -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; dkim=pass header.i=@infradead.org header.s=merlin.20170209 header.b=V4L7qO2R; 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 S1806102AbgJ0QFx (ORCPT + 99 others); Tue, 27 Oct 2020 12:05:53 -0400 Received: from merlin.infradead.org ([205.233.59.134]:51744 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1802140AbgJ0Ppp (ORCPT ); Tue, 27 Oct 2020 11:45:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=vS0WQyA1FoopoJORMaYRyN4NqXEhBztCAPdnx7wzKRQ=; b=V4L7qO2R2JS6pfVWkQymVaWMwj RmjAu/+KnCywtjZeZK9NVh+x0yEmTW0fFmGJ/vI4GFgqyf1KSr4f4DnxLB6XcnZRVvcFTZBE1pU2K PkpcGgFuFuA50BHrE/3PQijXYUPUEo65svNy/X64ptCQF1jsNXjZFOGiJpJo0P34Ms67tBGRFzanp 8qhK0j5vR3gFi3+q5LWdy7qxPPxKMOxw9OuGi9x3Uh3hnFTPSIBHGlcTteCxRDjNRr4QqtZuBgLyt TlcrZhtGUH8hkI1+fqVOmwRdJxetpEJy1Y//hMblbW0QhMYESRv5WcJcwRT6M+E5U/IcQq39HAh3i VVMxcvKw==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=noisy.programming.kicks-ass.net) by merlin.infradead.org with esmtpsa (Exim 4.92.3 #3 (Red Hat Linux)) id 1kXRAH-0004XO-B2; Tue, 27 Oct 2020 15:45:37 +0000 Received: from hirez.programming.kicks-ass.net (hirez.programming.kicks-ass.net [192.168.1.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by noisy.programming.kicks-ass.net (Postfix) with ESMTPS id D08993060F2; Tue, 27 Oct 2020 16:45:33 +0100 (CET) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id A7876203CF3A9; Tue, 27 Oct 2020 16:45:33 +0100 (CET) Date: Tue, 27 Oct 2020 16:45:33 +0100 From: Peter Zijlstra To: Chris Wilson Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org, tip-bot2 for Peter Zijlstra , Qian Cai , x86 Subject: Re: [tip: locking/core] lockdep: Fix usage_traceoverflow Message-ID: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <160380535006.10461.1259632375207276085@build.alporthouse.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?