lkml.org 
[lkml]   [2017]   [Oct]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/2] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default
On Thu, Oct 19, 2017 at 08:22:12AM +0200, Ingo Molnar wrote:
> There's no current crash regression that I know of - I'm just outlining the
> conditions of getting all this re-enabled in the next merge window.
>
> Instead of sending two series, could you please send a series that includes both
> these fixing + re-enabling patches, plus the false positive fixes?
>
> In particular I think the cross-release re-enabling should be done as the last
> patch, so that any future bisections of new false positives won't be made more
> difficult by re-introducing the old false positives near the end of the bisection.

I agree. But I already sent v2 before you told me..

Do you want me to send patches fixing false positives in the thread
fixing performance regression?

\
 
 \ /
  Last update: 2017-10-22 17:20    [W:0.637 / U:0.136 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site