On Tue, 2 Dec 2014 20:14:52 -0800 Linus Torvalds <torva...@linux-foundation.org> wrote:
> What is *really* suspicious is a series of "git bisect good" with no > "bad"s anywhere. Which is exactly what we see at the end of the > bisect. > > So might I ask you to try starting from this point again (this is why > the bisect log is so useful - no need to retest the above part, you > can just mindlessly do that sequence by hand without testing), and > starting with this commit: > > > # good: [47dfe4037e37b2843055ea3feccf1c335ea23a9c] Merge branch > > 'for-3.17' of > > git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup git bisect > > good 47dfe4037e37b2843055ea3feccf1c335ea23a9c > Of course, bugs can come in from anywhere, so it *could* be the > tracing one, and it *could* be the merge commit, but my gut just > screams that you probably missed one bad kernel, and marked it good. > And it's really that very first one (ie commit > 47dfe4037e37b2843055ea3feccf1c335ea23a9c) that contains most of the > actually suspect code, so I'd really like you to re-test that one a > lot before you call it "good" again. > > Humor me. > > I added Tejun to the Cc, just because I wanted to give him a heads-up > that I am tentatively starting to blame him in my dark little mind.. :) I understand Linus. I'll try the 47dfe4037 commit you suggested harder and I'll return tomorrow. -- Linux 3.16.0-00409-gb8c0aa4: Shuffling Zombie Juror http://www.youtube.com/DanielFragaBR http://exchangewar.info Bitcoin: 12H6661yoLDUZaYPdah6urZS5WiXwTAUgL -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/