From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755438AbbJANaA (ORCPT ); Thu, 1 Oct 2015 09:30:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59797 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751849AbbJAN36 (ORCPT ); Thu, 1 Oct 2015 09:29:58 -0400 Date: Thu, 1 Oct 2015 08:29:50 -0500 From: Josh Poimboeuf To: minipli@ld-linux.so Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org, live-patching@vger.kernel.org, Michal Marek , Peter Zijlstra , Andy Lutomirski , Borislav Petkov , Linus Torvalds , Andi Kleen , Pedro Alves , Namhyung Kim , Bernd Petrovitsch , Chris J Arges , Andrew Morton , Herbert Xu , "David S. Miller" Subject: Re: [PATCH v13 13/23] x86/asm/crypto: Create stack frames in aesni-intel_asm.S Message-ID: <20151001132950.GA4269@treble.redhat.com> References: <20151001061026.GA20908@ld-linux.so> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20151001061026.GA20908@ld-linux.so> User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 01, 2015 at 08:10:26AM +0200, minipli@ld-linux.so wrote: > On Tue, Sep 22, 2015 at 10:47:04AM -0500, Josh Poimboeuf wrote: > > aesni-intel_asm.S has several callable non-leaf functions which don't > > honor CONFIG_FRAME_POINTER, which can result in bad stack traces. > > > > Create stack frames for them when CONFIG_FRAME_POINTER is enabled. > > > > Signed-off-by: Josh Poimboeuf > > Cc: Herbert Xu > > Cc: David S. Miller > > --- > > arch/x86/crypto/aesni-intel_asm.S | 19 +++++++++++++++++++ > > 1 file changed, 19 insertions(+) > > > > diff --git a/arch/x86/crypto/aesni-intel_asm.S b/arch/x86/crypto/aesni-intel_asm.S > > index 6bd2c6c..289ef12 100644 > > --- a/arch/x86/crypto/aesni-intel_asm.S > > +++ b/arch/x86/crypto/aesni-intel_asm.S > > @@ -31,6 +31,7 @@ > > > > #include > > #include > > +#include > > > > /* > > * The following macros are used to move an (un)aligned 16 byte value to/from > > @@ -1800,6 +1801,7 @@ ENDPROC(_key_expansion_256b) > > * unsigned int key_len) > > */ > > > ENTRY(aesni_set_key) > > + FRAME_BEGIN > > #ifndef __x86_64__ > > pushl KEYP > > movl 8(%esp), KEYP # ctx > > This will break 32 bit builds using the aesni-intel.ko module. You need > to adjust the esp-based offsets for the non-x86_64 case, as FRAME_BEGIN > may do another push. > > How about adding a FRAME_OFFSET() macro to to wrap the > offsets?: > > #ifdef CONFIG_FRAME_POINTER > # define FRAME_OFFSET(x) ((x) + (BITS_PER_LONG / 8)) > #else > # define FRAME_OFFSET(x) (x) > #endif > > And using them like this: > > movl FRAME_OFFSET(8)(%esp), KEYP # ctx Ah, right. The 32-bit ABI passes arguments on the stack instead of via registers. For now, I'm inclined to just make FRAME_BEGIN and FRAME_END do nothing on 32-bit. We're only doing stack validation on x86_64 and I don't know if anybody cares about frame pointers on 32-bit at this point. -- Josh