linux-kernel - Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no stop-machine, update stack tracer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 04 Jan 2012 00:01:41 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no
 stop-machine, update stack tracer

On Tue, 2012-01-03 at 19:12 -0500, Steven Rostedt wrote:

> I should have tested this branch more. As I enabled BISECT_CHECK=1 in my
> ktest config, it boots both the bad commit and the good commit making
> sure the bad commit fails, and the good commit succeeds. The bad did
> fail, but so did the good commit, which was Linus's branch.
> 
> I booted it again just now, and it failed again.
> 
> I'll boot it a couple more times and maybe even recompile. Perhaps I
> didn't test Linus's branch correctly (checkout out the wrong branch?).

My mistake, I forgot to add the "minimum config" for booting the box.
When I did that, it booted fine. I kicked off the bisect again, and lets
see what happens.

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/