From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F2768C432C3 for ; Thu, 21 Nov 2019 19:27:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BB825206D7 for ; Thu, 21 Nov 2019 19:27:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726774AbfKUT1j (ORCPT ); Thu, 21 Nov 2019 14:27:39 -0500 Received: from mail.kernel.org ([198.145.29.99]:52344 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726293AbfKUT1j (ORCPT ); Thu, 21 Nov 2019 14:27:39 -0500 Received: from oasis.local.home (unknown [66.170.99.95]) (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 C61B22068F; Thu, 21 Nov 2019 19:27:38 +0000 (UTC) Date: Thu, 21 Nov 2019 14:27:37 -0500 From: Steven Rostedt To: Mark Rutland Cc: Torsten Duwe , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Ingo Molnar Subject: Re: KASAN_INLINE && patchable-function-entry Message-ID: <20191121142737.69978ef9@oasis.local.home> In-Reply-To: <20191121183630.GA3668@lakrids.cambridge.arm.com> References: <20191121183630.GA3668@lakrids.cambridge.arm.com> X-Mailer: Claws Mail 3.17.3 (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, 21 Nov 2019 18:36:32 +0000 Mark Rutland wrote: > As a heads-up to the ftrace folk, I think it's possible to work around > this specific issue in the kernel by allowing the arch code to filter > out call sites at init time (probably in ftrace_init_nop()), but I > haven't put that together yet. If you need to make some code invisible to ftrace at init time, it can be possible by setting the dyn_ftrace rec flag to DISABLED, but this can be cleared, which we would need a way to keep it from being cleared, which shouldn't be too hard. Is that what you would be looking for? -- Steve