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, 27 Sep 2010 21:26:53 +0200
From:	"N.P.S. N.P.S." <napohybelskurwysynom2010@...il.com>
To:	Paweł Sikora <pluto@...k.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: git bisect selects commit outside initial bisect range?

Hi,

W dniu 27 września 2010 20:51 użytkownik Paweł Sikora <pluto@...k.net> napisał:
> hi,
>
> i've noticed on kernel 2.6.35.y some weird screen blinking during
> e.g. <alt-tab> on kde4 with enabled accelerated desktop effects.
>
> i've started git bisect between good-v2.6.34 and bad-v2.6.35-rc1
> and after few steps git-bisect jumps to commit before v2.6.34.
>
> [~/src/linux/linux-2.6]$ make kernelrelease
> 2.6.34-rc6-00551-g7a6cb0d
>
> [~/src/linux/linux-2.6]$ git bisect log
> git bisect start
> # good: [e40152ee1e1c7a63f4777791863215e3faa37a86] Linus 2.6.34
> git bisect good e40152ee1e1c7a63f4777791863215e3faa37a86
> # bad: [67a3e12b05e055c0415c556a315a3d3eb637e29e] Linux 2.6.35-rc1
> git bisect bad 67a3e12b05e055c0415c556a315a3d3eb637e29e
> # good: [f8965467f366fd18f01feafb5db10512d7b4422c] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6
> git bisect good f8965467f366fd18f01feafb5db10512d7b4422c
> # bad: [d79df0b1eda0099a22cbcece01ce5e7d222450de] Merge git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6
> git bisect bad d79df0b1eda0099a22cbcece01ce5e7d222450de
> # good: [ac3ee84c604502240122c47b52f0542ec8774f15] Merge branch 'dbg-early-merge' of git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb
> git bisect good ac3ee84c604502240122c47b52f0542ec8774f15
>
> is it normal that bisect selects next step outside initial range?

It seems to me that it could happen - there are many merges of many
branches of the code - some of them may have really old commits.

>
> BR,
> Pawel.
>
> ps).
> please CC me on reply.
> --
> 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/
>



-- 
Slawa!
N.P.S.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ