From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755628AbcHSVz1 (ORCPT ); Fri, 19 Aug 2016 17:55:27 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45196 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754598AbcHSVzZ (ORCPT ); Fri, 19 Aug 2016 17:55:25 -0400 Date: Fri, 19 Aug 2016 16:55:22 -0500 From: Josh Poimboeuf To: Kees Cook Cc: Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , "x86@kernel.org" , LKML , Andy Lutomirski , Linus Torvalds , Steven Rostedt , Brian Gerst , Peter Zijlstra , Frederic Weisbecker , Byungchul Park , Nilay Vaish Subject: Re: [PATCH v4 54/57] x86/mm: convert arch_within_stack_frames() to use the new unwinder Message-ID: <20160819215522.ofav5ifdn7i5taxm@treble> References: <62fab36288792edae0181274641d6b4c62157fea.1471525031.git.jpoimboe@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0.1 (2016-04-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Fri, 19 Aug 2016 21:55:25 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 19, 2016 at 11:27:18AM -0700, Kees Cook wrote: > On Thu, Aug 18, 2016 at 6:06 AM, Josh Poimboeuf wrote: > > Convert arch_within_stack_frames() to use the new unwinder. > > > > This also changes some existing behavior: > > > > - Skip checking of pt_regs frames. > > - Warn if it can't reach the grandparent's stack frame. > > - Warn if it doesn't unwind to the end of the stack. > > > > Signed-off-by: Josh Poimboeuf > > All the stuff touching usercopy looks good to me. One question, > though, in looking through the unwinder. It seems like it's much more > complex than just the frame-hopping that the old > arch_within_stack_frames() did, but I'm curious to hear what you think > about its performance. We'll be calling this with every usercopy that > touches the stack, so I'd like to be able to estimate the performance > impact of this replacement... Yeah, good point. I'll take some measurements from before and after and get back to you. -- Josh