LKML Archive on
help / color / mirror / Atom feed
From: Steven Rostedt <>
To: Lukas Bulwahn <>
Cc: Ingo Molnar <>,
	Josh Poimboeuf <>,
	Jiri Kosina <>,,
	Peter Zijlstra <>,
	Miroslav Benes <>,,,
Subject: Re: [PATCH] tracing: define needed config DYNAMIC_FTRACE_WITH_ARGS
Date: Fri, 6 Aug 2021 21:18:08 -0400	[thread overview]
Message-ID: <20210806211808.6d927880@oasis.local.home> (raw)
In-Reply-To: <>

On Fri,  6 Aug 2021 21:50:27 +0200
Lukas Bulwahn <> wrote:

> Commit 2860cd8a2353 ("livepatch: Use the default ftrace_ops instead of
> REGS when ARGS is available") intends to enable config LIVEPATCH when
> ftrace with ARGS is available. However, the chain of configs to enable
> LIVEPATCH is incomplete, as HAVE_DYNAMIC_FTRACE_WITH_ARGS is available,
> but the definition of DYNAMIC_FTRACE_WITH_ARGS, combining DYNAMIC_FTRACE
> and HAVE_DYNAMIC_FTRACE_WITH_ARGS, needed to enable LIVEPATCH, is missing
> in the commit.
> Fortunately, ./scripts/ detects this and warns:
> Referencing files: kernel/livepatch/Kconfig
> So, define the config DYNAMIC_FTRACE_WITH_ARGS analogously to the already
> existing similar configs, DYNAMIC_FTRACE_WITH_REGS and
> DYNAMIC_FTRACE_WITH_DIRECT_CALLS, in ./kernel/trace/Kconfig to connect the
> chain of configs.
> Fixes: 2860cd8a2353 ("livepatch: Use the default ftrace_ops instead of REGS when ARGS is available")
> Cc: <> # 5.10.x

FYI, we don't add # 5.10.x anymore. The Fixes tag above is what
determines where it gets backported to.

> Signed-off-by: Lukas Bulwahn <>
> ---
> Steven, thanks for the quick response; please pick this quick config fix.

I placed it in my queue to go into the 5.14-rc cycle.

Since this affects live kernel patching, can I get a Tested-by from one
of the live kernel patching  folks?


-- Steve

  reply	other threads:[~2021-08-07  1:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06 19:50 Lukas Bulwahn
2021-08-07  1:18 ` Steven Rostedt [this message]
2021-08-17  9:28   ` Miroslav Benes
2021-08-17 13:37     ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210806211808.6d927880@oasis.local.home \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] tracing: define needed config DYNAMIC_FTRACE_WITH_ARGS' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).