linux-kernel - Re: GIT bisection range errors

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:	Fri, 09 May 2008 00:36:55 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Adrian Bunk <bunk@...nel.org>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: GIT bisection range errors

On 09-05-08 00:25, Adrian Bunk wrote:
> On Fri, May 09, 2008 at 12:20:16AM +0200, Rene Herman wrote:
>> Good day.
>>
>> I'm in a git bisect and am experiencing strangeness. I did a
>>
>> $ git checkout -b rc v2.6.26-rc1
>> $ git bisect start
>> $ git bisect bad
>> $ git bisect good v2.6.25
>>
>> Yet, during this I'm finding myself at 2.6.25-rc6 and 2.6.25-rc8
>> as the last two results (both good...).
>>
>> Here's the BISECT_LOG upto this point. Is there anyone available
>> who understands this well enough to be able to say from this that
>> my tree is fubar? It should be a straight Linus' clone, and it's
>> always pulling without trouble.
>>
>> git-bisect start
>> # bad: [2ddcca36c8bcfa251724fe342c8327451988be0d] Linux 2.6.26-rc1
>> git-bisect bad 2ddcca36c8bcfa251724fe342c8327451988be0d
>> # good: [4b119e21d0c66c22e8ca03df05d9de623d0eb50f] Linux 2.6.25
>> git-bisect good 4b119e21d0c66c22e8ca03df05d9de623d0eb50f
>> # bad: [7ae44cfa7ab29b277691327e8de790d7b880722f] [ALSA] snd-powermac: style awacs.s and awacs.h
>> git-bisect bad 7ae44cfa7ab29b277691327e8de790d7b880722f
>> # good: [7cea51be4e91edad05bd834f3235b45c57783f0d] security: fix up documentation for security_module_enable
>> git-bisect good 7cea51be4e91edad05bd834f3235b45c57783f0d
>> # bad: [8f19ca1341a6d89bd96e2e69e6e10f46d3258089] x86: unify gfp masks
>> git-bisect bad 8f19ca1341a6d89bd96e2e69e6e10f46d3258089
>> # good: [f49e1aa133c2c9b74b5dfddca8863609bbda9086] [NETFILTER]: nf_conntrack_sip: update copyright
>> git-bisect good f49e1aa133c2c9b74b5dfddca8863609bbda9086
>> # good: [0b18542b7f5379e052d2a3132be91185776e7ceb] [NET]: Sink IPv6 menuoptions into its own submenu
>> git-bisect good 0b18542b7f5379e052d2a3132be91185776e7ceb
> 
> Don't trust any dates you see in git.  ;-)
> 
> The last commit in your list was added to David's tree at around the 
> time Linus released Linux 2.6.25-rc7.
> 
> But David's tree was merged into Linus' tree after 2.6.25.
> 
> So actually everything is fine.

Well, thanks for the reply and I'm going forward for now, but the Makefile
is actually calling this 2.6.25-rc8. My next "git bisect good" after the
above landed me now after 2.6.25 according to the Makefile. It could just
be a tags issue I guess, where my tree is confused about what tag belongs
to v2.6.25?

(new two lines in the log)

# good: [ba380013b681e91e059f95b51002f8d43024b371] b43: Add fastpath to b43_mac_suspend()
git-bisect good ba380013b681e91e059f95b51002f8d43024b371

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