linux-kernel - Re: help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related

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:	Wed, 1 Sep 2010 20:47:16 +0200
From:	Paolo Ornati <ornati@...il.com>
To:	Martin Steigerwald <Martin@...htvoll.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: help with git bisecting a bug 16376: random - possibly Radeon
 DRM KMS related - freezes

On Tue, 31 Aug 2010 21:53:43 +0200
Martin Steigerwald <Martin@...htvoll.de> wrote:

> Obviously I am not interested in kernels prior 2.6.33. Should I just do a 
> "git bisect good" without trying the kernel or is there some other remedy? 

No. Git is right in asking you to test that commit: you are ignoring
branches and merges.

Example
========

Linus Tree	Usb Tree

v2.6.33-rc2
|          \
|           | commit A (version is v2.6.33-rc2)
|           | commit B ( " )
v2.6.33     | commit C ( " )
|        __/
|     __/
|  __/
|_/
X <--- MERGE

So the commit you are testing it's like "commit A": it was done before
(in time) v2.6.33, on a kernel based on v2.6.33-rc2, but was merged in
Linus' tree _after_ v2.3.33.

So this this behaviour is normal :)

-- 
	Paolo Ornati
	Linux 2.6.35.4 on x86_64
--
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/