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.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,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 CB21FC432C0 for ; Thu, 21 Nov 2019 19:27:43 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9BEE9206D7 for ; Thu, 21 Nov 2019 19:27:43 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="VEAIGjSj" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9BEE9206D7 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=0XqgEUV44PDeMSSLKxzG6lXBdqRV4ojWH3ezi8B5kyA=; b=VEAIGjSjFC31TY EV+f39G4zxaq6rb3v27niy2jPhSAM0rxCQM2QsNbwtDy2+dFRkEqEnaNhjOd6FC6E1cCobOHr4F9m gDlIvDuSV0ITtvKCOLnsm/eLqVemsz0jLwaHw/NgalAfiV48Kpt151tPNTvhbVDm3DvDaGMA/nY2I 9j7TN57ZiGkgTG45UT/9mN5r99yQ7I8Stkyn9U7w25VQPxkIqQFxgBN67sfPgLuU9Q2yiHWbyNqIa sl+UoeUAHE6NN6YIcOYRWenel+LSTRw6wuFp9W0JPnIdnI3LPmvmbuG3PrHCd0GcET1OkYDFsd8qW 88xklMKveWqMPyyNTsZw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1iXs7C-0005ql-1g; Thu, 21 Nov 2019 19:27:42 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1iXs79-0005qA-Q1 for linux-arm-kernel@lists.infradead.org; Thu, 21 Nov 2019 19:27:41 +0000 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 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 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20191121_112739_863463_E1C43D70 X-CRM114-Status: GOOD ( 10.58 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Torsten Duwe , Ingo Molnar , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.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 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel