DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
        b=bmH6jZBOpyyejjwGNWi7txPoWmpb2AyMUOi9zogrRk85CH3K9CLWJoG5cKH4NzU94P
         ut5GS2z4xdyEhGG3IA5uDhYtwQB0yUEgD4zb08/DlNXF83CGohO9bnIB3eLw0A54lXIu
         wEAEHBXIhUDfGWb7i2zwOUDd2Zlt3I9vl31Gk=
MIME-Version: 1.0
In-Reply-To: <20101109181525.GH5876@outflux.net>
References: <20101109181157.GE5876@outflux.net>
	<20101109181525.GH5876@outflux.net>
Date: Tue, 9 Nov 2010 21:09:18 +0200
Message-ID: <AANLkTimzAaj1Z-jyCLBPKGzp_PWw2hwkYy_XeLo8CKPP@mail.gmail.com>
Subject: Re: [PATCH 3/4] x86: call verify_cpu during 32bit CPU startup
From: Pekka Enberg <penberg@kernel.org>
To: Kees Cook <kees.cook@canonical.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 594
Lines: 13

On Tue, Nov 9, 2010 at 8:15 PM, Kees Cook <kees.cook@canonical.com> wrote:
> The XD_DISABLE-clearing side-effect needs to happen on 32bit CPU
> start-up as well.
>
> Signed-off-by: Kees Cook <kees.cook@canonical.com>

The patch description here is pretty damn terse. Why do we need the
clearing for? Does not clearing XD_DISABLE cause some problem?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/