From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource/drivers/ti-32k: Prevent ftrace recursion
Date: Thu, 22 Sep 2016 15:58:03 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1609221555590.5599@nanos> (raw)
In-Reply-To: <20160922075621.3725-1-jszhang@marvell.com>
On Thu, 22 Sep 2016, Jisheng Zhang wrote:
> Currently ti-32k can be used as a scheduler clock. We properly marked
> omap_32k_read_sched_clock() as notrace but we then call another
> function ti_32k_read_cycles() that _wasn't_ notrace.
>
> Having a traceable function in the sched_clock() path leads to a
> recursion within ftrace and a kernel crash.
Kernel crash? Doesn't ftrace core prevent recursion?
Thanks,
tglx
next prev parent reply other threads:[~2016-09-22 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 7:56 [PATCH] clocksource/drivers/ti-32k: Prevent ftrace recursion Jisheng Zhang
2016-09-22 13:58 ` Thomas Gleixner [this message]
2016-09-22 14:29 ` Steven Rostedt
2016-09-23 2:04 ` Jisheng Zhang
2016-09-23 2:45 ` Steven Rostedt
2016-09-23 2:48 ` Jisheng Zhang
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=alpine.DEB.2.20.1609221555590.5599@nanos \
--to=tglx@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.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