Messages in this thread | | | Date | Sun, 10 Feb 2019 22:23:45 +0100 (CET) | From | Thomas Gleixner <> | Subject | Re: [PATCH] x86/alternatives: check int3 breakpoint physical addresses |
| |
On Fri, 25 Jan 2019, Alexandre Chartre wrote: > Note that this issue has been observed and reproduced with a custom kernel > with some code mapped to different virtual addresses and using jump labels > As jump labels use text_poke_bp(), crashes were sometimes observed when > updating jump labels.
Rightfully so. text_poke_bp() pokes at the kernels text mapping which is very well defined and unique. Why would you map the same text to different virtual addresses and then use a randomly chosen one to poke at it?
Thanks,
tglx
| |