[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160530074001.GA2620@pd.tnic>
Date: Mon, 30 May 2016 09:40:01 +0200
From: Borislav Petkov <bp@...en8.de>
To: Andy Lutomirski <luto@...capital.net>
Cc: Brian Gerst <brgerst@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
X86 ML <x86@...nel.org>, Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH 4/7] x86/dumpstack: If addr_limit is non-default, display
it
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.
Powered by blists - more mailing lists