Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp837996imd; Thu, 1 Nov 2018 06:25:14 -0700 (PDT) X-Google-Smtp-Source: AJdET5eV57K/zSyVPZmdnJDhg04Pq9JG0SiLnn7qHE2iJHaP1XXIrNbtk7LEzlSFhajX3iUP5+cF X-Received: by 2002:a17:902:6b88:: with SMTP id p8-v6mr7411210plk.19.1541078714920; Thu, 01 Nov 2018 06:25:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541078714; cv=none; d=google.com; s=arc-20160816; b=D+ub/Z3xfu3P2Cu3w+xaBdtxhN/S950OPKcfgkt0wN6byBQuln+Mztu7cmEKpBOrx4 ws7lJYj+Cifx9NYE1LejQQBG4E/PjOaSGMfi25ltp6Ut7IGP1+Ws/49yMnZVHWNm2Ig/ QEIZYRGXdaW0+TpXk3Snn2Dp/w+85ibSNs+9MEvyg1iU4hfbEr9e7AJPunRTrxT8JRrJ mZ4d6fNmnl45sehQCNg1kVypMa8+PU0PlA0kiRrh+W6+uMcvT2lRBoAflMsVsl2FtRRj z0a563SEpuD4UkJXs55N7VgXs8Oo37hPHvwObtr/ksWbQFIQSANMMdWSKeNKDMPkzxVf 4U8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=k0ZAqGvLXM9YmcILVu3eh+2BOJlsgtNa8nrQokjr75Y=; b=MGCfxvD2knH135RaHV/AUi3K9FpJIn6XCemh6i5zJItQ5Rulz/Tkpd3FSV6ahdhOvB eAhxda4xLvaoGDMHyZhoHFtjlrBGS+uv7CFEiR42SdNwDbt1lee+jH/qBxugaK+pLMJp 0uE+3rYd2f0s6l4Rb4FeLtPIngaiLCm24x2VWL4NBm5RwYULQU8Yv5ALOS9gPePyAMbJ df0ozwjkGKyQkPC8xAPs/VZXMo+kvoRXeamPZ1hut0h2hdjxGiEvX+Pn6YAtisQTcIXd O0SyK3LzbWE3qWkCPEDRU2ZnljaKxwFlhadkEH/GWo7PnOo6oeNSaRPhlW3zo3OHLkYB MyNg== 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 e92-v6si30360660pld.45.2018.11.01.06.24.56; Thu, 01 Nov 2018 06:25:14 -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 S1728514AbeKAWZo (ORCPT + 99 others); Thu, 1 Nov 2018 18:25:44 -0400 Received: from mail.kernel.org ([198.145.29.99]:46138 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727644AbeKAWZo (ORCPT ); Thu, 1 Nov 2018 18:25:44 -0400 Received: from vmware.local.home (unknown [12.156.218.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 116012081B; Thu, 1 Nov 2018 13:22:45 +0000 (UTC) Date: Thu, 1 Nov 2018 09:22:44 -0400 From: Steven Rostedt To: Aleksa Sarai Cc: Masami Hiramatsu , "Naveen N. Rao" , Anil S Keshavamurthy , "David S. Miller" , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Alexander Shishkin , Jiri Olsa , Namhyung Kim , Brendan Gregg , Christian Brauner , Aleksa Sarai , linux-kernel@vger.kernel.org Subject: Re: [PATCH] kretprobe: produce sane stack traces Message-ID: <20181101092244.2ad82f18@vmware.local.home> In-Reply-To: <20181101104948.bc7wk453bfryhhk7@yavin> References: <20181026132210.12569-1-cyphar@cyphar.com> <20181030101206.2e5998ca3c75496c91ba5b09@kernel.org> <20181031090317.4e211fdd@vmware.local.home> <20181031133912.3j5tryq2vyhkdn4d@yavin> <20181101191347.74eadff4a5d1fab2d79d7efe@kernel.org> <20181101104948.bc7wk453bfryhhk7@yavin> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 1 Nov 2018 21:49:48 +1100 Aleksa Sarai wrote: > > > Should I continue working on this patchset? > > > > Yes, until we finally introduce Steven's algorithm on all arch (yeah, we still > > have some archs which don't support graph-tracer but supports kprobes), > > I think your patch is the best fix for this issue. Agreed. > > Thanks, I just sent a v3. Thanks. Hopefully I can take a look at it today or tomorrow. I'm still trying to get home (sitting at yet another airport as I write this). > > Though, even with Steven's hooking of kprobes I think you'd still need > to stash away the stack trace somewhere (or am I misunderstanding the > proposal?). I'll start working on it and then we can see what is needed when there is actual code. I need to probably change the func graph generic interface which will require changes in all the archs that support function graph tracer. -- Steve