From owner-freebsd-security@FreeBSD.ORG  Thu Jun 14 00:27:20 2012
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 4F561106564A
	for <freebsd-security@freebsd.org>;
	Thu, 14 Jun 2012 00:27:20 +0000 (UTC)
	(envelope-from delphij@delphij.net)
Received: from anubis.delphij.net (anubis.delphij.net [64.62.153.212])
	by mx1.freebsd.org (Postfix) with ESMTP id 32EBC8FC14
	for <freebsd-security@freebsd.org>;
	Thu, 14 Jun 2012 00:27:20 +0000 (UTC)
Received: from delta.delphij.net (unknown [206.40.55.65])
	(using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
	(No client certificate requested)
	by anubis.delphij.net (Postfix) with ESMTPSA id E38EAF6BB;
	Wed, 13 Jun 2012 17:27:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis;
	t=1339633639; bh=sqftKMATfogYYRPeNncyGcxN1kTKi66cVm8ofRf0ViU=;
	h=Date:From:Reply-To:To:CC:Subject:References:In-Reply-To;
	b=hdg0zj3UKaOskf+vN/JZz/DMhtoMGrVxnsZuk/TQZvDWabNwZJtD5X71FSAt7vcGt
	R1D7bCGZk2a7r8Lun26+2joX7TatgkeVHrdl6BqaeCnPF1p+d2+myQP3idVNG5uu2n
	FxmYP3MFamABJwhvzuKHpVX3urYdJR/roZ80GBKk=
Message-ID: <4FD92FD6.1090007@delphij.net>
Date: Wed, 13 Jun 2012 17:27:02 -0700
From: Xin Li <delphij@delphij.net>
Organization: The FreeBSD Project
MIME-Version: 1.0
To: Greg Lewis <glewis@eyesbeyond.com>
References: <201206121326.q5CDQXca078536@freefall.freebsd.org>
	<20120613223758.GA72817@misty.eyesbeyond.com>
In-Reply-To: <20120613223758.GA72817@misty.eyesbeyond.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-security@freebsd.org, d@delphij.net
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-12:04.sysret
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: d@delphij.net
List-Id: "Security issues \[members-only posting\]"
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2012 00:27:20 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 06/13/12 15:37, Greg Lewis wrote:
> On Tue, Jun 12, 2012 at 01:26:33PM +0000, FreeBSD Security
> Advisories wrote:
>> IV.  Workaround
>> 
>> No workaround is available.
>> 
>> However FreeBSD/amd64 running on AMD CPUs is not vulnerable to
>> this particular problem.
>> 
>> Systems with 64 bit capable CPUs, but running the 32 bit
>> FreeBSD/i386 kernel are not vulnerable, nor are systems running
>> on different processor architectures.
> 
> I found these last two paragraphs a little confusing.  Is the
> correct interpretation that FreeBSD/amd64 running on Intel CPUs is
> the vulnerable combination?

Correct.

Cheers,
- -- 
Xin LI <delphij@delphij.net>	https://www.delphij.net/
FreeBSD - The Power to Serve!		Live free or die


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQEcBAEBCAAGBQJP2S/WAAoJEG80Jeu8UPuz9JMIALQwTqb6SDKAUwLkxupOgyEa
7dSHYAxwbNWKNvjbK0brS05kx5RdEmxdkoRqdKOlPcY8JnbqpbROWIbUHA8XIfCW
igHIISTgQhiw5nx8XqMMoEfzztPR7UKr9rE+CToWLT8GbHWEpiYlE1RpIQgoZ0TK
ldlQSOOMZ32zushxbM1ZncSM0/Rm9ie+ISezGfCV/lXqQUycVxnxjV/Euf6OKzxC
xQC2nI21UIu1nZi8sfT0Qnlz8o/ehEYMmHDJgkphxLxMqtWW6l/WqdPMtEGWwBVB
rBGRVQvkCrqu8aKBUsOFmX9+vZ4riDtggrXjSadAUGVQNMtBlHBPJ83vmyiQ5LA=
=Qpu0
-----END PGP SIGNATURE-----