linux-kernel - Re: [PATCH 1/2] [for 3.4] drivers/virt: the Freescale hypervisor driver doesn't need to check MSR[GS]

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: <AB770BBF-9E2B-461F-B0A9-F141517EBEDD@kernel.crashing.org>
Date:	Sun, 25 Nov 2012 07:07:31 -0600
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Timur Tabi <timur@...escale.com>
Cc:	<linuxppc-dev@...ux.freescale.net>,
	Scott Wood <scottwood@...escale.com>,
	Anatolij Gustschin <agust@...x.de>, <geert@...ux-m68k.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] [for 3.4] drivers/virt: the Freescale hypervisor driver doesn't need to check MSR[GS]


On May 17, 2012, at 2:10 PM, Timur Tabi wrote:

> The MSR[GS] bit indicates whether the kernel is running in processor guest
> state mode, but such a check is unnecessary.  The driver already checks
> for the /hypervisor node and the fsl,hv-version property, so it already
> knows that it's running under the Freescale hypervisor.
> 
> There is nothing in the driver that inherently requires guest state,
> anyway.
> 
> This fixes a break that can occur in some randconfig builds.
> 
> Signed-off-by: Timur Tabi <timur@...escale.com>
> ---
> drivers/virt/fsl_hypervisor.c |    3 ---
> 1 files changed, 0 insertions(+), 3 deletions(-)

applied to next

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