On Thu, Apr 12, 2018 at 3:47 PM, Kees Cook <keesc...@chromium.org> wrote:
> After fixing up some build issues in the middle of the 4.16 cycle, I
> get an unhelpful bisect result of commit 0a4b6e2f80aa ("Merge branch
> 'for-4.16/block'"). Instead of letting the test run longer, I'm going
> to switch to doing several shorter test boots per kernel and see if
> that helps. One more bisect coming...Okay, so I can confirm the bisect points at the _merge_ itself, not a specific patch. I'm not sure how to proceed here. It looks like some kind of interaction between separate trees? Jens, do you have suggestions on how to track this down? -Kees -- Kees Cook Pixel Security
