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 S932477AbcE2Smq (ORCPT <rfc822;w@1wt.eu>);
	Sun, 29 May 2016 14:42:46 -0400
Received: from mail.skyhub.de ([78.46.96.112]:45595 "EHLO mail.skyhub.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S932315AbcE2Smp (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Sun, 29 May 2016 14:42:45 -0400
User-Agent: K-9 Mail for Android
In-Reply-To: <CALCETrW6LWrUUD085+vwEVti4OCdNt=cRj+jwQO93xJHE5EgSQ@mail.gmail.com>
References: <cover.1464129798.git.luto@kernel.org> <be65c2feeaed23b29fbe92c24088a1aa793fe999.1464129798.git.luto@kernel.org> <20160525113927.GC4420@pd.tnic> <CALCETrW6LWrUUD085+vwEVti4OCdNt=cRj+jwQO93xJHE5EgSQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH 4/7] x86/dumpstack: If addr_limit is non-default, display it
From: Boris Petkov <bp@alien8.de>
Date: Sun, 29 May 2016 20:42:40 +0200
To: Andy Lutomirski <luto@amacapital.net>
CC: Andy Lutomirski <luto@kernel.org>, X86 ML <x86@kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Kees Cook <keescook@chromium.org>, Brian Gerst <brgerst@gmail.com>
Message-ID: <e1454076-faac-47d1-823f-416950c22e28@email.android.com>
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Andy Lutomirski <luto@amacapital.net> wrote:
>Easier said than done.  struct thread_info doesn't have addr_limit on
>sensible architectures (e.g. sparc), and I'd rather not stick a bunch
>of ifdefs in generic code.

It's not like it doesn't have an actual address limit though - I'm guessing it is something like the max userspace address on the arch... UINT_MAX or somesuch.
-- 
Sent from a small device: formatting sux and brevity is inevitable.