RFC x86: Catch stray non-kprobe breakpoints
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 15 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | x86: Move in_kprobes_functions to linux/kprobes.hinclude/ kernel/ | +9 | 0 replies | |
| 2/3 | x86: Macrofy resuable codearch/ | +9 | 2 replies | |
| 3/3 | x86: WARN_ON breakpoints from .kprobes.text sectionarch/ | +9 | 5 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3][RFC] x86: Catch stray non-kprobe breakpoints
Greetings,
Non kprobe breakpoints in the kernel might lie inside the .kprobes.text section. Such breakpoints can easily be identified by in_kprobes_functions and can be caught early. These are problematic and a warning should be emitted to discourage them (in any rare case, if they actually occur).
For this, a check can route the trap handling of such breakpoints away from kprobe_handler (which ends up calling even more functions marked as __kprobes) from inside kprobe_exceptions_notify.
All comments/suggestions are welcome.
--
Thanks & Regards,
Abhishek Sagar