MIME-Version: 1.0
In-Reply-To: <BFF945FF-4FA2-41B1-8527-7CB954020A88@zytor.com>
References: <CALCETrUqdp=rEKX4gdSpJYder3q0g_yxdRE9APw8MgerXvnB=w@mail.gmail.com>
 <CAMzpN2h_1m3wcSpvNxC4FyOrDBnn50Estwk_v_zc7=NNGxW_zg@mail.gmail.com>
 <CALCETrU7voFkTpKmyo2ujEAuEUVOg3r-FKspnCWXQ-pXpQamDg@mail.gmail.com>
 <20161121071342.GA16999@gmail.com> <CA+55aFwH8zQNj42LyqFTbXqU+nUbDgDhqMW+so_-OPpM5SRwuQ@mail.gmail.com>
 <5bc7c7b2-875e-6366-9244-7dc6e2fae5c1@zytor.com> <CA+55aFwKd4X-hio7KOdVYHhm6KzO0-2y2-2-YjxeKWb=evj9=Q@mail.gmail.com>
 <BFF945FF-4FA2-41B1-8527-7CB954020A88@zytor.com>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Mon, 21 Nov 2016 14:25:34 -0800
Message-ID: <CA+55aFzCGJD50mkKwsgqWtGJ-NN_sB9GCvxDFY3ZpEoz_oEeiQ@mail.gmail.com>
Subject: Re: What exactly do 32-bit x86 exceptions push on the stack in the CS slot?
To: Peter Anvin <hpa@zytor.com>
Cc: Ingo Molnar <mingo@kernel.org>, Andy Lutomirski <luto@amacapital.net>,
        Brian Gerst <brgerst@gmail.com>, Andy Lutomirski <luto@kernel.org>,
        tedheadster@gmail.com, George Spelvin <linux@horizon.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        X86 ML <x86@kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 354
Lines: 9

On Mon, Nov 21, 2016 at 2:17 PM,  <hpa@zytor.com> wrote:
>
> Now, segment loads have always ignored the top 32 bits; it's an issue when examined by other kinds of code.

Yes. Particularly ptrace and signal information copying. Need to make
sure those things don't look at (or expose) high bits that may be
stale stack contents etc.

               Linus