Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2199537pxb; Mon, 18 Jan 2021 10:47:44 -0800 (PST) X-Google-Smtp-Source: ABdhPJwDUvbYxoEbWrPvFqe15WFhbZHddH+fr0sFqj6qgTGetwMhbVWo/DOB3ZlhtV86oSuoTU3Z X-Received: by 2002:a17:906:6449:: with SMTP id l9mr726611ejn.320.1610995664632; Mon, 18 Jan 2021 10:47:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610995664; cv=none; d=google.com; s=arc-20160816; b=j7TTXfWbYHXd04E6HajH837u9EYZtgfnnEZ9xNykdUsT7MlTBuZnxqFEUATX4GLnhs kEjeMYW/6uGoZERxZERWyQbWXvSPcS2D1nkj+xnBmItgtsTBw/o1YuD7SZKSvletEGuL hJdxkgI+e4YBuPgW2EWu48xV+l8kqiJO7hyypXnb2yZyoC9jjLFNw7mnUty7NgFolLil v4+cRs879v7o/2nuXQx0F6V6aEvNVoFsp8KxHnC34t1VizCiH70tYT5SyhiAT4A51nBA k44Shi/p8xI8j9jyFUGaLhqTdoqWydULBsmo++dCSZU1Nmeu5tXDVg9ZKuZ2HC72S4MT yxKQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=XfddDMCi1Pxl3W6f+Db2b3gwKQfbFtA72kEelMHy2z4=; b=Y5kowSUY08dsC3ccyGWkt459xf6aotgf/b1g37+ruEeVDc4ixKtTD+ZL9WbEpcZUfH VuFCmdfbRfA7stRcZnLNMD5YTI0ebiZT/ky8yJXSmB+LeOCyuEAhki6fx/lhlIcFnlxH 2N5SOQ1BFFoDCrFJDGZCzCliKS/d4Ix/IlxX8hFfCvSaBTWWhcd90rjWbvxzgJluq9gw +/iaedUUSjwbLkCWhHRCYloiFXrUG3AjDM6tjT56hmURUhoTLgV4QDTH7kpWKhkc3k7f VRqXqwbjg8d2GIWWS9klqVmoHPqqT4JAahiGNrMWlRmOsDQ4jp3bpXoHheDWc+GxS1zZ 8Sig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=tRtZQAla; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dd11si1081746edb.36.2021.01.18.10.47.21; Mon, 18 Jan 2021 10:47:44 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=tRtZQAla; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2393737AbhARSoU (ORCPT + 99 others); Mon, 18 Jan 2021 13:44:20 -0500 Received: from mail.kernel.org ([198.145.29.99]:36096 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390694AbhARLlK (ORCPT ); Mon, 18 Jan 2021 06:41:10 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 8203C22227; Mon, 18 Jan 2021 11:40:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1610970054; bh=w7B5f9uenIacxZFGsisM9l2ZEYOQEfKWdv2aS+20kVY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=tRtZQAla47mtesGkYEyoHF9RztVEOWCW5Y0v5BnP9eDfHyz+Z86+QdZ4+RtcW9wTv RnEXw9PutcSo//0TpeN/TkB40AcmgufpWVofTH1PxBriZESKNSakhJfvECdG/cqCWn a2oeq+Ovp/mBETVB1qCLFfhEx52OrFmxcnOZc3HU= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, "Naveen N. Rao" , Masami Hiramatsu , "Steven Rostedt (VMware)" Subject: [PATCH 5.10 018/152] tracing/kprobes: Do the notrace functions check without kprobes on ftrace Date: Mon, 18 Jan 2021 12:33:13 +0100 Message-Id: <20210118113353.645230259@linuxfoundation.org> X-Mailer: git-send-email 2.30.0 In-Reply-To: <20210118113352.764293297@linuxfoundation.org> References: <20210118113352.764293297@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Masami Hiramatsu commit 7bb83f6fc4ee84e95d0ac0d14452c2619fb3fe70 upstream. Enable the notrace function check on the architecture which doesn't support kprobes on ftrace but support dynamic ftrace. This notrace function check is not only for the kprobes on ftrace but also sw-breakpoint based kprobes. Thus there is no reason to limit this check for the arch which supports kprobes on ftrace. This also changes the dependency of Kconfig. Because kprobe event uses the function tracer's address list for identifying notrace function, if the CONFIG_DYNAMIC_FTRACE=n, it can not check whether the target function is notrace or not. Link: https://lkml.kernel.org/r/20210105065730.2634785-1-naveen.n.rao@linux.vnet.ibm.com Link: https://lkml.kernel.org/r/161007957862.114704.4512260007555399463.stgit@devnote2 Cc: stable@vger.kernel.org Fixes: 45408c4f92506 ("tracing: kprobes: Prohibit probing on notrace function") Acked-by: Naveen N. Rao Signed-off-by: Masami Hiramatsu Signed-off-by: Steven Rostedt (VMware) Signed-off-by: Greg Kroah-Hartman --- kernel/trace/Kconfig | 2 +- kernel/trace/trace_kprobe.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) --- a/kernel/trace/Kconfig +++ b/kernel/trace/Kconfig @@ -531,7 +531,7 @@ config KPROBE_EVENTS config KPROBE_EVENTS_ON_NOTRACE bool "Do NOT protect notrace function from kprobe events" depends on KPROBE_EVENTS - depends on KPROBES_ON_FTRACE + depends on DYNAMIC_FTRACE default n help This is only for the developers who want to debug ftrace itself --- a/kernel/trace/trace_kprobe.c +++ b/kernel/trace/trace_kprobe.c @@ -434,7 +434,7 @@ static int disable_trace_kprobe(struct t return 0; } -#if defined(CONFIG_KPROBES_ON_FTRACE) && \ +#if defined(CONFIG_DYNAMIC_FTRACE) && \ !defined(CONFIG_KPROBE_EVENTS_ON_NOTRACE) static bool __within_notrace_func(unsigned long addr) {