[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191016102504.274fc88d@gandalf.local.home>
Date: Wed, 16 Oct 2019 10:25:04 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Miroslav Benes <mbenes@...e.cz>
Cc: mingo@...hat.com, jpoimboe@...hat.com, jikos@...nel.org,
pmladek@...e.com, joe.lawrence@...hat.com,
linux-kernel@...r.kernel.org, live-patching@...r.kernel.org,
shuah@...nel.org, kamalesh@...ux.vnet.ibm.com,
linux-kselftest@...r.kernel.org
Subject: Re: [PATCH v3 1/3] ftrace: Introduce PERMANENT ftrace_ops flag
On Wed, 16 Oct 2019 09:48:53 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> @@ -6796,10 +6798,12 @@ ftrace_enable_sysctl(struct ctl_table *table, int write,
>
> ret = proc_dointvec(table, write, buffer, lenp, ppos);
As you just stated on IRC, the update to ftrace_enabled gets updated in
the above routine.
I forgot about this :-/ (Senior moment)
I guess there's nothing to worry about here.
-- Steve
>
> - if (ret || !write || (last_ftrace_enabled == !!ftrace_enabled))
> + if (ret || !write || (ftrace_enabled == !!sysctl_ftrace_enabled))
> goto out;
>
Powered by blists - more mailing lists