| 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
| ||
|
Message-ID: <3e8340490910061809k6ed6d463v3e357bd703013dca@mail.gmail.com> Date: Tue, 6 Oct 2009 21:09:18 -0400 From: Bryan Donlan <bdonlan@...il.com> To: Frans Pop <elendil@...net.nl> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, hohndel@...radead.org, linux-kernel@...r.kernel.org Subject: Re: Linux 2.6.32-rc3 On Tue, Oct 6, 2009 at 12:36 PM, Frans Pop <elendil@...net.nl> wrote: > BTW, I've got a solution for bisection too: the versions in the Makefile > get changed to something constant. And the package version is set equal to > the bisection iteration. This ensures that I know exactly which kernels > were build for the series and that I can always go back to a specific > kernel if I need to retest for some reason. > > E.g. (for a bisection covering .30-.31): > linux-image-2.6.31-bisect_1_amd64.deb > linux-image-2.6.31-bisect_2_amd64.deb > linux-image-2.6.31-bisect_3_amd64.deb It should be noted that implementing this would result in the package names becoming wildly inconsistent if you bisect over the point where this feature is introduced. In order to be useful, it would need to determine if its own implementation commit is shadowed by the 'bisect good' marker, make a note of this in a non-overwritten location (.git, eg), then disable itself and use the old behavior if it would bisect over its own introduction. -- 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