linux-kernel - Re: 2.6.19-rc <-> ThinkPads

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]

Message-ID: <Pine.LNX.4.64.0610312123320.25218@g5.osdl.org>
Date:	Tue, 31 Oct 2006 21:26:12 -0800 (PST)
From:	Linus Torvalds <torvalds@...l.org>
To:	Ernst Herzberg <earny@...4u.de>
cc:	Len Brown <lenb@...nel.org>, Adrian Bunk <bunk@...sta.de>,
	Hugh Dickins <hugh@...itas.com>,
	"Michael S. Tsirkin" <mst@...lanox.co.il>,
	Pavel Machek <pavel@...e.cz>, Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-acpi@...r.kernel.org, linux-pm@...l.org,
	Martin Lorenz <martin@...enz.eu.org>
Subject: Re: 2.6.19-rc <-> ThinkPads

On Wed, 1 Nov 2006, Ernst Herzberg wrote:
> 
> still bisecting, will report the result.

Figuring out what caused an apparent change of behaviour is definitely a 
good idea - it might give us some clue to what really is going on.

(Or it might not. Sometimes the patch that triggers changes really doesn't 
seem to have anything to do with anything, and it literally was just a 
latent bug that just happened to be exposed by something that had nothing 
to do with anything at all but perhaps timing. But that's pretty rare in 
the end. It happens, but it's definitely not the common case at all, and I 
think it's great that you're bisecting even if there is a possibility 
that we'll be left with a big "Huh? Whaa?" as the end result ;^)

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