ftrace: prevent ftrace modifications while being kprobe'd
Status from this message: applied to tip/tracing/ftrace, thanks Abhishek.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | ftrace: store mcount address in rec->iparch/ arch/ arch/ +16 more | +110 | 0 replies | |
| 2/4 | kprobes: enable clean usage of get_kprobeinclude/ | +4 | 1 reply | |
| 3/4 | ftrace: avoid modifying kprobe'd recordskernel/ | +31 | 0 replies | |
| 4/4 | ftrace: freeze kprobe'd recordsinclude/ kernel/ kernel/ | +87 | 0 replies |
Reviews trailers per patch
1 of 4 patches has a Reviewed-by or Acked-by.
| Patch | Ananth N Mavinakayanahalli |
|---|---|
| 1/4 | |
| 2/4 | A-b |
| 3/4 | |
| 4/4 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] ftrace: prevent ftrace modifications while being kprobe'd
Hi Steven/Ingo,
These patches address the problem of kprobe registration interfering with dynamic ftrace. A kprobe registered on an mcount call-site can modify that address multiple times during its duration of probing. At the same time, ftrace may simultaneously modify these locations. This could be fatal especially if ftrace modifies the call-site during a kprobe registration on it (between arch_prepare_kprobe and arch_arm_kprobe in __register_kprobe to be more precise). So as a "fix", I've disabled any updates on the mcount call-site while it's being kprobe'd.
--
Regards,
Abhishek Sagar