Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1427790
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: chain_key collision with 4.7.0-rec2+ |
| Date | 2016-06-21 16:10 +0200 |
| Message-ID | <rMuxk-6S0-3@gated-at.bofh.it> (permalink) |
| References | <rMtUC-6nL-41@gated-at.bofh.it> <rMtUC-6nL-43@gated-at.bofh.it> <rMtUC-6nL-39@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: chain_key collision with 4.7.0-rec2+ David Ahern <dsa@cumulusnetworks.com> - 2016-06-21 15:30 +0200 Re: chain_key collision with 4.7.0-rec2+ Peter Zijlstra <peterz@infradead.org> - 2016-06-21 16:10 +0200
csiph-web