linux-kernel - Re: help to bisect

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: <20110518072245.GB17608@liondog.tnic>
Date:	Wed, 18 May 2011 09:22:45 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	James <bjlockie@...kie.ca>
Cc:	Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: help to bisect

On Tue, May 17, 2011 at 08:27:16PM -0400, James wrote:
> How do I build v2.6.36 so I can test it mark it good so I can bisect?
> 
> Here is what I want to do:
> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.37.y.git
> $ cd linux-2.6.37.y
> $ git bisect start
> $ git bisect good v2.6.36
> $ git bisect bad v2.6.37.6
> 
> Do I do "git checkout v2.6.36"?

Yes, but you should do it first, before starting bisection. After you've
verified .36 is fine, then you do the last three commands:

> $ git bisect start
> $ git bisect good v2.6.36
> $ git bisect bad v2.6.37.6

assuming you have verified also that .37.6 is bad, but I guess so,
otherwise you wouldn't be bisecting in the first place :)

Also, it might make sense to check whether .37 is fine too before
bisecting. If so, you save yourself quite a bit of bisection runs by
marking .37 as good instead of .36.

HTH.

-- 
Regards/Gruss,
    Boris.
--
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/