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]

Message-ID: <1325635922.12696.8.camel@gandalf.stny.rr.com>
Date:	Tue, 03 Jan 2012 19:12:02 -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:02 -0500, Steven Rostedt wrote:

> I then looked at the merge you did with Linus's branch:
> 
> c7f46b7aa4ae5cbef32eb5e016512a14f936affa
> 
> Checked that out, and booted it twice with your config, and it booted
> without failure both times.

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?).

Thanks,

-- 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/