linux-kernel - Re: [PATCH -next] fork and exit: need to include iocontext.h

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] [day] [month] [year] [list]

Message-Id: <20080701103417.c0c09538.sfr@canb.auug.org.au>
Date:	Tue, 1 Jul 2008 10:34:17 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>, linux-next@...r.kernel.org,
	lkml <linux-kernel@...r.kernel.org>, mingo <mingo@...hat.com>,
	tglx <tglx@...utronix.de>, hpa <hpa@...or.com>,
	akpm <akpm@...ux-foundation.org>,
	Jens Axboe <jens.axboe@...cle.com>
Subject: Re: [PATCH -next] fork and exit: need to include iocontext.h

On Mon, 30 Jun 2008 20:33:37 +0200 Ingo Molnar <mingo@...e.hu> wrote:
>
> normally there's an easy way to find out the source commit of build 
> failures. Try something like:
> 
>  git-bisect reset
>  git-bisect start
>  git-bisect good v2.6.26-rc8

More generally "git-bisect good linux-next/stable" - the stable branch is
just where I started on Linus' tree and that is always good :-)

>  git-bisect bad linux-next/master
>  git-bisect run make kernel/fork.o
> 
> ... this should lead you to the commit that broke the build 
> automatically. (as long as everyone keeps make oldconfig compatibility)

Nice, I must try this.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped