linux-kernel - Re: Wierdness - linux-next KVM patch breaks Dell Latitude D820, KVM not in kernel

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:	Wed, 09 Sep 2009 13:34:50 -0400
From:	Valdis.Kletnieks@...edu
To:	Beth Kon <eak@...ibm.com>, rostedt@...dmis.org, avi@...hat.com,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Wierdness - linux-next KVM patch breaks Dell Latitude D820, KVM not in kernel

On Tue, 08 Sep 2009 15:41:28 EDT, Valdis.Kletnieks@...edu said:

> Yeah, I was quite confused by the bisect results as well, I may end up
> re-doing it just to make sure I didn't screw something up along the way (since
> I started it with -rc7/HEAD as the good/bad, but most of the resulting
> kernels reported a pre-rc7 release (a 2.6.28 at one point, IIRC, and it
> finished at 31-rc2.

I've become convinced that Something Really Bad happened to the KVM tree in
linux-next on its way to my laptop - after 2 bisects, it reported I had some
2,000 commits left to check.  So I ran 'git bisect visualize' to sanity check.

And *every single one* of those 4,000 commits between 'good' and 'bad' was a
KVM commit, stretching all the way back to 2007.  Unless that's an artifact
of the way linux-next is built, I would have expected only "new-ish" commits
to be in the bisect window, and not just out of one tree...

So I ended up doing a 'WTF?', an 'rm -r', and am cloning over today's linux-next
and will see if that brings me any better joy.

Content of type "application/pgp-signature" skipped