linux-kernel - Re: 2.6.25-rc3-mm1 - BUG at system shutdown time

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, 21 Mar 2008 14:41:28 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Valdis.Kletnieks@...edu
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.25-rc3-mm1 - BUG at system shutdown time


* Valdis.Kletnieks@...edu <Valdis.Kletnieks@...edu> wrote:

> I may have to try again to figure out how to bisect the git-x86 tree - 
> Ingo send me a pointer to his git-x86 cheat sheet, I looked at it but 
> I couldn't figure out how to tell 'git bisect' that the starting good 
> spot was "whatever corresponded to the git-x86 patch in 24-rc8-mm1" 
> and bad was "25-rc3-mm1". I tried using the first commit ID listed in 
> the patch, but that gave me this:

the best way to bisect the x86.git-only commits is to do:

  git-bisect bad x86/latest
  git-bisect good x86/base

the 'base' branch is the upstream tree that x86.git is based against. 
This will minimize the number of bisection points as well, because 
you'll only bisect x86.git patches.

[ and make sure you test x86/base first to establish that it's truly
  'good' :-) ]

	Ingo
--
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/