From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752127AbcFUOCe (ORCPT ); Tue, 21 Jun 2016 10:02:34 -0400 Received: from merlin.infradead.org ([205.233.59.134]:45704 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751722AbcFUOCb (ORCPT ); Tue, 21 Jun 2016 10:02:31 -0400 Date: Tue, 21 Jun 2016 16:02:20 +0200 From: Peter Zijlstra To: David Ahern Cc: Ingo Molnar , LKML Subject: Re: chain_key collision with 4.7.0-rec2+ Message-ID: <20160621140220.GD3704@worktop> References: <8650ca98-24e9-20c3-f1e5-033ccdface2f@cumulusnetworks.com> <20160621131335.GP30154@twins.programming.kicks-ass.net> <476f1719-6fab-88fe-11ab-8e1d738275e3@cumulusnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <476f1719-6fab-88fe-11ab-8e1d738275e3@cumulusnetworks.com> User-Agent: Mutt/1.5.22.1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 21, 2016 at 07:22:38AM -0600, David Ahern wrote: > On 6/21/16 7:13 AM, Peter Zijlstra wrote: > >But if you're really annoyed by it all, disable DEBUG_LOCKDEP for a > >while and rest assured that its not more broken than it was before -- > >just louder :-) > > > > Not really an option if I want to make sure I am not adding locking issues > and the habit of ignoring splats defeats the purpose of enabling the lock > debugging. So hopefully you come up with a better answer. > DEBUG_LOCKDEP is lockdep debugging, disabling that does not disable lockdep itself. Just a 'few' internal consistency checks.