[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250219095330.2e9f171c@gandalf.local.home>
Date: Wed, 19 Feb 2025 09:53:30 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, Mark
Rutland <mark.rutland@....com>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, Andrew Morton
<akpm@...ux-foundation.org>, Heiko Carstens <hca@...ux.ibm.com>, Sven
Schnelle <svens@...ux.ibm.com>, Vasily Gorbik <gor@...ux.ibm.com>,
Alexander Gordeev <agordeev@...ux.ibm.com>, stable@...r.kernel.org
Subject: Re: [PATCH 4/5] fprobe: Always unregister fgraph function from ops
On Wed, 19 Feb 2025 09:57:15 +0900
Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:
> Good catch! I forgot to remove the filter in this case.
> Is there anyway to be sure the filter is empty or clear it if
> fprobe_graph_active == 0?
You can call ftrace_free_filter(), but you need to make sure that the ops
is not active. Hmm, I should add a warning and exit if the ops is active
when that function is called.
-- Steve
Powered by blists - more mailing lists