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 21:12:11 +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:

> On Fri, 21 Mar 2008 20:58:13 BST, Ingo Molnar said:
> 
> > no, we frequently regenerate the x86.git tree so the dates have little 
> > relevance. If for any particular pull, x86/base is good and x86/latest 
> > is bad, then the bug is somewhere in those 200-300 patches inbetween. 
> > They are lined up linearly so should be perfectly bisectable.
> 
> OK, off to go try the last few bisects then...

well ... your git bisection log does look suspiciously 'good', so 
something is wrong thee i think :-(

the chance to get 8 'good' bisection points in a row is 1:256. OTOH, the 
freshest x86 patches are always at the 'end' of the queue - which are 
also the ones most likely to break anything.

Are you sure the x86/base point is indeed 'good'? You can check it via:

 git-checkout -b tmp x86/base

and build+boot it.

	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/