From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
Shuah Khan <shuah@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH 2/4] ftrace/instances: Clear function triggers when removing instances
Date: Wed, 17 May 2017 01:11:15 +0900 [thread overview]
Message-ID: <20170517011115.3e5e6d74a0602fcc2467c886@kernel.org> (raw)
In-Reply-To: <20170515121103.65b811cb@gandalf.local.home>
On Mon, 15 May 2017 12:11:03 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 15 May 2017 11:21:15 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Sun, 14 May 2017 01:01:02 +0530
> > "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:
> >
> > > If instance directories are deleted while there are registered function
> > > triggers:
> > >
> > > # cd /sys/kernel/debug/tracing/instances
> > > # mkdir test
> > > # echo "schedule:enable_event:sched:sched_switch" > test/set_ftrace_filter
> > > # rmdir test
> > > Unable to handle kernel paging request for data at address 0x00000008
> > > Unable to handle kernel paging request for data at address 0x00000008
> > > Faulting instruction address: 0xc0000000021edde8
> > > Oops: Kernel access of bad area, sig: 11 [#1]
> > > SMP NR_CPUS=2048
> > > NUMA
> > > pSeries
> >
> > Looks like this patch needs to be marked for stable, and go in right
> > away. I may also do the same for the ftracetest bashism patch with
> > Masami's approval. I may also slip in the ftracetest for the bug that
> > this patch fixes.
>
> As this patch fixes a bug that was introduced with the 4.12 merge
> window. Thus, it's not stable worthy (stable isn't affected). Although,
> I'll wait on Masami to see if that should go to stable.
Hm, for the bashism fix, that is not a show-stopper... and also,
newer ftracetest should work on older kernel. So I don't think
it needs to go stable.
Thank you,
>
> -- Steve
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2017-05-16 16:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 19:31 [PATCH 0/4] ftrace: Fix a few issues Naveen N. Rao
2017-05-13 19:31 ` [PATCH 1/4] ftrace: Simplify glob handling in unregister_ftrace_function_probe_func() Naveen N. Rao
2017-05-15 17:22 ` Steven Rostedt
2017-05-16 8:07 ` Naveen N. Rao
2017-05-13 19:31 ` [PATCH 2/4] ftrace/instances: Clear function triggers when removing instances Naveen N. Rao
2017-05-15 15:21 ` Steven Rostedt
2017-05-15 16:11 ` Steven Rostedt
2017-05-16 16:11 ` Masami Hiramatsu [this message]
2017-05-16 2:20 ` Steven Rostedt
2017-05-16 14:01 ` Naveen N. Rao
2017-05-16 17:44 ` Naveen N. Rao
2017-05-16 18:33 ` Steven Rostedt
2017-06-06 17:06 ` Shuah Khan
2017-06-06 17:37 ` Naveen N. Rao
2017-05-13 19:31 ` [PATCH 3/4] selftests/ftrace: Fix bashisms Naveen N. Rao
2017-05-15 15:16 ` Steven Rostedt
2017-05-16 14:25 ` Masami Hiramatsu
2017-05-13 19:31 ` [PATCH 4/4] selftests/ftrace: Add test to remove instance with active event triggers Naveen N. Rao
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170517011115.3e5e6d74a0602fcc2467c886@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox