linux-kernel - Re: [YASB] Re: Linux 3.7-rc7

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: <20121205214851.GA11443@rhlx01.hs-esslingen.de>
Date:	Wed, 5 Dec 2012 22:48:51 +0100
From:	Andreas Mohr <andi@...as.de>
To:	Andreas Mohr <andi@...as.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [YASB] Re: Linux 3.7-rc7

Hi,

got through all steps after all, and the ghost vanished.

Perhaps I did some silly mistake (marked that original master HEAD
as "bad" despite not actually having run that but rather some local
seemingly innocuous modifications - that will teach me for sure...).

Or perhaps it was something about the weird (to put it mildly) gcc ICEs
that I got when doing next bisection build on *some* of those kernels...
(i.e., some earlier effects from that, thus causing the problem)
A memtest run would be in order...
(fortunately I'm one generation post magnetic core memory on this "box" :-))

Just saw the -rc8 announce, thus I wanted to clarify status now,
but I'm still only 98% solid about this bisection result here.
Probably best to go straight ahead to -rc8.

Andreas Mohr
--
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/