linux-kernel - Re: Need help debugging RT-preempt patch

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] [day] [month] [year] [list]

Message-ID: <463FC24C.309@third-harmonic.com>
Date:	Mon, 07 May 2007 20:20:28 -0400
From:	john cooper <john.cooper@...rd-harmonic.com>
To:	Daniel Walker <dwalker@...sta.com>
CC:	Tim Bird <tim.bird@...sony.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, dirk.behme@...glemail.com,
	linux kernel <linux-kernel@...r.kernel.org>,
	john cooper <john.cooper@...rd-harmonic.com>
Subject: Re: Need help debugging RT-preempt patch

Daniel Walker wrote:

> I'm not sure I'd get into "bisecting" one big patch. Especially if you
> new to the patches inner workings.. 
> 
> You can bisect by kernel version using the older patches but it's
> clearly limited,
> 
> http://people.redhat.com/mingo/realtime-preempt/older/

Actually working on this more closely over a year or so ago I
found a binary chop among patch versions to often be the
fastest means of locating the source of breakage.  Though that
may have been more applicable when several patch versions per
day were being generated.

-john

-- 
john.cooper@...rd-harmonic.com
-
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/