From: Peter Zijlstra <peterz@infradead.org>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: Ingo Molnar <mingo@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: chain_key collision with 4.7.0-rec2+
Date: Tue, 21 Jun 2016 16:02:20 +0200 [thread overview]
Message-ID: <20160621140220.GD3704@worktop> (raw)
In-Reply-To: <476f1719-6fab-88fe-11ab-8e1d738275e3@cumulusnetworks.com>
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.
prev parent reply other threads:[~2016-06-21 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 13:03 chain_key collision with 4.7.0-rec2+ David Ahern
2016-06-21 13:13 ` Peter Zijlstra
2016-06-21 13:22 ` David Ahern
2016-06-21 14:02 ` Peter Zijlstra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160621140220.GD3704@worktop \
--to=peterz@infradead.org \
--cc=dsa@cumulusnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.