Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp2081607ybd; Thu, 27 Jun 2019 06:29:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqzLYqdlM0vgio/5/18iolfKoRjZg1lMjobCTUR0RHGWaFIONbiV/bMwW5dPZGlsSChVr9Dy X-Received: by 2002:a63:dc56:: with SMTP id f22mr3846076pgj.305.1561642176276; Thu, 27 Jun 2019 06:29:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561642176; cv=none; d=google.com; s=arc-20160816; b=WP3dbUx/XEOxc+0xQWk+Nuo/Ei9Mm/UD5uMws30asvsJG3GTlojv9HV6Gvfd0m9xn4 o2Y4u87DVQF/sQJnXvP6dZt2zNsvE1m3yMvM/436fGcuMVHW1pOGIVMedkG92/9vG+of +yeJ/BMEr6KV9B0lyHVAWb3uMHiEWOcIV/HuR7JwYqpZWWdl5toCa+37YyejrLS8BtlJ p0S+rA6/Y8vtXPtrSh+GefIf6FZNcXGk2ZCVjmwaXpFKZc36jCjibPF90muZu/npWt7u IAhYgeDdlm8e8QiNedRtFtLIOOLnmPIpSIlFnXBtT4PN6Dj4CEVdqSMAv4M/2peRiafk aLgQ== 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=CHpKhWdezCeipA4tsZaO9XrApBryiuoTPCrKJ9lrV+4=; b=o/mLou/ASIJtFS5KpM5qiAo7Wm5hiZVi6MLChUfMFMzoF4vNZQ3UqAFvr4tapK51+d BSuMujLA5zJvMZe2dxQEYm4wP7t0qQ3lfcLFkEwSY+rTmwfdl5P32UUnkC6TSMCWN82U 7aF0AoEY4Jc3+6MkP1mIEGnx+RDYP084zOaX9zUN5Uf5I8Xf6q/jFoiNrLfRHitVJ7W+ /IAAujJvTr28E9FW1kZ52USc0I9ZlfFhcTOodw2J7YBsVO0+Gp+d0+8s5aAgV2nuAjVV aucS/OV5Db4MmOzbqbkkViYJmAkwG9kcScTvNvIl4kwTBp+adICaN5z4pTUKPEdMftTN WNKg== 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 f21si1869360pgv.381.2019.06.27.06.29.18; Thu, 27 Jun 2019 06:29:36 -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 S1726716AbfF0N3F (ORCPT + 99 others); Thu, 27 Jun 2019 09:29:05 -0400 Received: from mail.kernel.org ([198.145.29.99]:45274 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726370AbfF0N3F (ORCPT ); Thu, 27 Jun 2019 09:29:05 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (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 9CF132083B; Thu, 27 Jun 2019 13:29:03 +0000 (UTC) Date: Thu, 27 Jun 2019 09:29:02 -0400 From: Steven Rostedt To: "Naveen N. Rao" Cc: Michael Ellerman , Masami Hiramatsu , Ingo Molnar , Nicholas Piggin , , Subject: Re: [PATCH v2 2/7] x86/ftrace: Fix use of flags in ftrace_replace_code() Message-ID: <20190627092902.253971d2@gandalf.local.home> In-Reply-To: References: 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, 27 Jun 2019 16:53:50 +0530 "Naveen N. Rao" wrote: > In commit a0572f687fb3c ("ftrace: Allow ftrace_replace_code() to be > schedulable), the generic ftrace_replace_code() function was modified to > accept a flags argument in place of a single 'enable' flag. However, the > x86 version of this function was not updated. Fix the same. > > Fixes: a0572f687fb3c ("ftrace: Allow ftrace_replace_code() to be schedulable") I don't mind this change, but it's not a bug, and I'm not sure it should have the fixes tag. The reason being, the FTRACE_MODIFY_ENABLE_FL is only set when ftrace is called by with the command flag FTRACE_MAY_SLEEP, which is never done on x86. That said, I'm fine with the change as it makes it more robust, but by adding the fixes tag, you're going to get this into all the stable code, and I'm not sure that's really necessary. -- Steve > Signed-off-by: Naveen N. Rao > --- > arch/x86/kernel/ftrace.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/arch/x86/kernel/ftrace.c b/arch/x86/kernel/ftrace.c > index 0927bb158ffc..f34005a17051 100644 > --- a/arch/x86/kernel/ftrace.c > +++ b/arch/x86/kernel/ftrace.c > @@ -573,8 +573,9 @@ static void run_sync(void) > local_irq_disable(); > } > > -void ftrace_replace_code(int enable) > +void ftrace_replace_code(int mod_flags) > { > + int enable = mod_flags & FTRACE_MODIFY_ENABLE_FL; > struct ftrace_rec_iter *iter; > struct dyn_ftrace *rec; > const char *report = "adding breakpoints";