From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932609AbcE3HkM (ORCPT <rfc822;w@1wt.eu>);
	Mon, 30 May 2016 03:40:12 -0400
Received: from mail.skyhub.de ([78.46.96.112]:51864 "EHLO mail.skyhub.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752648AbcE3HkL (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 30 May 2016 03:40:11 -0400
Date: Mon, 30 May 2016 09:40:01 +0200
From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Brian Gerst <brgerst@gmail.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        X86 ML <x86@kernel.org>, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH 4/7] x86/dumpstack: If addr_limit is non-default, display
 it
Message-ID: <20160530074001.GA2620@pd.tnic>
References: <cover.1464129798.git.luto@kernel.org>
 <be65c2feeaed23b29fbe92c24088a1aa793fe999.1464129798.git.luto@kernel.org>
 <20160525113927.GC4420@pd.tnic>
 <CALCETrW6LWrUUD085+vwEVti4OCdNt=cRj+jwQO93xJHE5EgSQ@mail.gmail.com>
 <e1454076-faac-47d1-823f-416950c22e28@email.android.com>
 <CALCETrVg_LeHu3iCa-yGT6NubF6Vxo338wfytG-jWa0_+mmgmg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CALCETrVg_LeHu3iCa-yGT6NubF6Vxo338wfytG-jWa0_+mmgmg@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Sun, May 29, 2016 at 12:08:29PM -0700, Andy Lutomirski wrote:
> Sure, but how do I implement that?  There's no "does this arch have
> addr_limit in thread_info" general flag that I know of.

What about get_fs()? Looks like all arches implement that and on sparc
it is something called thread_info.current_ds...

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.