linux-kernel - Re: 2.6.22-rc5 regression

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:	Mon, 18 Jun 2007 11:35:03 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Carlo Wood <carlo@...noe.com>
cc:	Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org,
	eric@...olt.net, zhenyu.z.wang@...el.com, lethal@...ux-sh.org,
	y-goto@...fujitsu.com
Subject: Re: 2.6.22-rc5 regression



On Mon, 18 Jun 2007, Carlo Wood wrote:
> 
> I suppose you mean: ... then you WILL get sensible values out of git
> bisect. But, since I already did a real "git bisect" without giving it
> random points, I am afraid you jumped conclusions.

Hey, fair enough.

That said, your "git bisect" really *does* act oddly.

> However, I can easily reproduce it. From my history file I can see that I started with:
> 
>    git bisect start
>    git bisect bad v2.6.22-rc5
>    git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa

Goodie. 

> I wrote everything down on paper (the git id's and whether they
> were good or bad), so I can reproduce it with:

I can follow along, but I get *totally*different* git bisection points!

> hikaru:/usr/src/kernel/git/linux-2.6>git bisect start
> hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad v2.6.22-rc5
> hikaru:/usr/src/kernel/git/linux-2.6>git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
> Bisecting: 128 revisions left to test after this
> D       include/asm-blackfin/macros.h
> M       scripts/package/Makefile
> D       scripts/package/builddeb

You seem to have a modified tree! What are those modifications to the 
blackfin macros.h etc files?

You *should* have gotten this:

	[torvalds@...dy linux]$ git bisect start
	[torvalds@...dy linux]$ git bisect bad v2.6.22-rc5
	[torvalds@...dy linux]$ git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
	Bisecting: 127 revisions left to test after this
	[9808901b6c63a1c850b072e624c228901a9eaf10] Blackfin serial driver: ignore framing and parity errors

but those are just off by one, at least (127 vs 128 commits left).

> [cf68676222e54cd0a31efd968da00e65f9a0963f] Blackfin serial driver: actually implement the break_ctl() function
> hikaru:/usr/src/kernel/git/linux-2.6>git bisect good
> Bisecting: 111 revisions left to test after this

And that's totally broken. Even if I don't use the "9808901b6" commit, and 
use your "cf686762" commit, I get:

	[torvalds@...dy linux]$ git bisect good cf68676222e54cd0a31efd968da00e65f9a0963f
	Bisecting: 63 revisions left to test after this
	[aba297927d1d558c7a94548135133bdf9172708a] Merge master.kernel.org:/pub/scm/linux/kernel/git/kyle/parisc-2.6

Notice? The "127 revisions left to test after this" has become "63 
revisions left to test after this".

That number should be cut in half each time. And you shouldn't get some 
strange dirty tree indications.

It might be worth it just making sure your git is ok. It really is acting 
oddly. What version is it?

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