Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp3657788ybh; Mon, 5 Aug 2019 23:05:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqx0BJd/zu1sfY6PO9WBcuNDui5WuPi0G+4VJ6yshTMaaH/juFuFojVn8szRqfBnc4KpXF5X X-Received: by 2002:a63:a35e:: with SMTP id v30mr1463618pgn.129.1565071525834; Mon, 05 Aug 2019 23:05:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565071525; cv=none; d=google.com; s=arc-20160816; b=rHUyGRC0/6WNAW5TAO5OLr42geeZy4svheG490yVsGmynWXQxewURH6nPLVP2cMiT6 2kLKbUCRS13ZOtJiOt9SfL4i+6JlcI6Ljul5iwXlyh2lVV48aXojm4dnuSn6s7sKLZuN UAtYDMqL3a/H4/K9eI0jK5NsFGXRqRWV9PJXOQPvqnWqnk0s+Jo2IfpBk4okAmkPWGBE 2a1+gqZDjSc4fiGOyA+l/Bbkee5uJA/oJr9hn2NexEAGzQSMHmC+QqmR3qbZ2gG1ZKrd XeraPl9B8rdnBzQM2SGEiKHtOSwi+9Wa/Mq6QnSfJCBjWwuybGZFcaI5bka8ZdW8jQJw +qaw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=G4sj6mykhSNDwtIWBerNFHIf7W8tPnVrOUpVfN6nuvM=; b=pTGPbyv17IGikpiXkD1VuPAghMl3rilXjknAkqPX/dctD029B601KCOFYuu3l8p+4v 0sRMq26jjg0X8xBz/0LeIt3EGPUcNvoDZXlKEweyb8xTPIzkP4xaC19sEIjUpqzUIq0W XWMEPwkq3sD5snh6U36xD/1GEKTgG7X2rn2LQh5aMuXNRve846foeb9JUe7/BXkSpGlO CYW7vwfoaRNS1VGRpzMRWPbF73glxPFh0E5iNVgOxFfS1QL8JBDySJyzCKRfKEHCkQC6 617LsruwwM7Ib9IfQd8y0wdVYdgHtjJd9gzSi4XVCvmIeHtb/aPdGNmzrnxlIo3/CVv4 6hlA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z191si45292762pgd.572.2019.08.05.23.05.09; Mon, 05 Aug 2019 23:05:25 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731749AbfHFGEX (ORCPT + 99 others); Tue, 6 Aug 2019 02:04:23 -0400 Received: from mail5.windriver.com ([192.103.53.11]:44180 "EHLO mail5.wrs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731560AbfHFGEN (ORCPT ); Tue, 6 Aug 2019 02:04:13 -0400 Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail5.wrs.com (8.15.2/8.15.2) with ESMTPS id x7661oZn031960 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 5 Aug 2019 23:02:00 -0700 Received: from [128.224.162.237] (128.224.162.237) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.3.468.0; Mon, 5 Aug 2019 23:01:39 -0700 Subject: Re: [PATCH v3] tracing: Function stack size and its name mismatch in arm64 To: Steven Rostedt CC: , , , , , References: <20190802094103.163576-1-jiping.ma2@windriver.com> <20190802112259.0530a648@gandalf.local.home> <20190802120920.3b1f4351@gandalf.local.home> From: Jiping Ma Message-ID: <50eb7362-1f61-71a2-0a89-5d3bf054716e@windriver.com> Date: Tue, 6 Aug 2019 14:01:37 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20190802120920.3b1f4351@gandalf.local.home> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019年08月03日 00:09, Steven Rostedt wrote: > On Fri, 2 Aug 2019 11:22:59 -0400 > Steven Rostedt wrote: > >> I think you are not explaining the issue correctly. From looking at the >> document, I think what you want to say is that the LR is saved *after* >> the data for the function. Is that correct? If so, then yes, it would >> cause the stack tracing algorithm to be incorrect. >> > [..] > >> Can someone confirm that this is the real issue? > Does this patch fix your issue? Yes, it does. -- Jiping > > -- Steve > > diff --git a/arch/arm64/include/asm/ftrace.h b/arch/arm64/include/asm/ftrace.h > index 5ab5200b2bdc..13a4832cfb00 100644 > --- a/arch/arm64/include/asm/ftrace.h > +++ b/arch/arm64/include/asm/ftrace.h > @@ -13,6 +13,7 @@ > #define HAVE_FUNCTION_GRAPH_FP_TEST > #define MCOUNT_ADDR ((unsigned long)_mcount) > #define MCOUNT_INSN_SIZE AARCH64_INSN_SIZE > +#define ARCH_RET_ADDR_AFTER_LOCAL_VARS 1 > > #ifndef __ASSEMBLY__ > #include > diff --git a/kernel/trace/trace_stack.c b/kernel/trace/trace_stack.c > index 5d16f73898db..050c6bd9beac 100644 > --- a/kernel/trace/trace_stack.c > +++ b/kernel/trace/trace_stack.c > @@ -158,6 +158,18 @@ static void check_stack(unsigned long ip, unsigned long *stack) > i++; > } > > +#ifdef ARCH_RET_ADDR_AFTER_LOCAL_VARS > + /* > + * Most archs store the return address before storing the > + * function's local variables. But some archs do this backwards. > + */ > + if (x > 1) { > + memmove(&stack_trace_index[0], &stack_trace_index[1], > + sizeof(stack_trace_index[0]) * (x - 1)); > + x--; > + } > +#endif > + > stack_trace_nr_entries = x; > > if (task_stack_end_corrupted(current)) { > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel