linux-kernel - Re: WARNING: at vsmp_64.c: is_vsmp

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: <20120823065137.GA30156@WorkStation.localnet>
Date:	Thu, 23 Aug 2012 09:51:37 +0300
From:	Ido Yariv <ido@...ery.com>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	Shai Fultheim <shai@...lemp.com>, Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: WARNING: at vsmp_64.c: is_vsmp_box()

Hi Fengguang,

On Thu, Aug 23, 2012 at 08:55:15AM +0800, Fengguang Wu wrote:
> Hi Ido,
> 
> The below warning should be introduced by this commit at tip/master:
> 
> commit c00679af441c5be76e195deed2c76fef65a5d102
> Author:     Ido Yariv <ido@...ery.com>
> CommitDate: Wed Aug 22 10:48:05 2012 +0200
> 
>     x86/vsmp: Use hypervisor layer for initialization
>    
> [    0.000000] tsc: Detected 3200.098 MHz processor
> [    0.000000] ------------[ cut here ]------------
> [    0.000000] WARNING: at /c/kernel-tests/src/tip/arch/x86/kernel/vsmp_64.c:158 is_vsmp_box+0xa1/0xb0()
> [    0.000000] Hardware name: Bochs
> [    0.000000] Pid: 0, comm: swapper/0 Not tainted 3.6.0-rc2-01612-g595b3f3 #292
> [    0.000000] Call Trace:
> [    0.000000]  [<ffffffff8105a12a>] ? warn_slowpath_common+0x7a/0xb0
> [    0.000000]  [<ffffffff810339f1>] ? is_vsmp_box+0xa1/0xb0
> [    0.000000]  [<ffffffff818125d5>] ? apic_is_clustered_box+0x34/0x4c
> [    0.000000]  [<ffffffff8180baa4>] ? unsynchronized_tsc+0x23/0x71
> [    0.000000]  [<ffffffff81f8330c>] ? tsc_init+0xc2/0xed
> [    0.000000]  [<ffffffff81f7cc0d>] ? start_kernel+0x3fd/0x47a
> [    0.000000]  [<ffffffff81f7c627>] ? repair_env_string+0x5b/0x5b
> [    0.000000]  [<ffffffff81f7c436>] ? x86_64_start_kernel+0x105/0x114

If another hypervisor is detected, vsmp's detect callback will not be
called, triggering this warning.

This commit is is no longer in tip for other reasons, but this issue
will be addressed in the next revision of this patch.

Thanks,
Ido.
--
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/