linux-kernel - VMI broken on tip/master...

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-next>] [day] [month] [year] [list]

Message-Id: <1236966968.14680.15.camel@alok-dev1>
Date:	Fri, 13 Mar 2009 10:56:08 -0700
From:	Alok Kataria <akataria@...are.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	the arch/x86 maintainers <x86@...nel.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: VMI broken on tip/master...

Hi Peter, 

I was seeing a early fault when running tip/master with VMI enabled on
VMware platform. 
This early fault was in the vmi_patch code where we are applying
paravirt_alternatives. After some trials i noticed that this is
reproducible only with CONFIG_TRACING. With that disabled my VM boots
again. 

I started a git bisect after that, and git pointed to this as the bad
commit

commit 6cc3c6e12bb039047974ad2e7e2d46d15a1b762f
    trace_clock: fix preemption bug

I then reverted that commit from tip/master and the system did boot. 
But I fail to understand how this simple patch would be causing things
to fail in VMI. Any ideas ?

Thanks,
Alok

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