Re: [PATCH] x86/alternatives: check int3 breakpoint physical addresses

2019-02-21 Thread Alexandre Chartre
On 02/11/2019 10:57 AM, Alexandre Chartre wrote: On 02/11/2019 10:15 AM, Thomas Gleixner wrote: On Mon, 11 Feb 2019, Alexandre Chartre wrote: On 02/10/2019 10:23 PM, Thomas Gleixner wrote: On Fri, 25 Jan 2019, Alexandre Chartre wrote: Note that this issue has been observed and reproduced w

Re: [PATCH] x86/alternatives: check int3 breakpoint physical addresses

2019-02-11 Thread Alexandre Chartre
On 02/11/2019 10:15 AM, Thomas Gleixner wrote: On Mon, 11 Feb 2019, Alexandre Chartre wrote: On 02/10/2019 10:23 PM, Thomas Gleixner wrote: 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 differ

Re: [PATCH] x86/alternatives: check int3 breakpoint physical addresses

2019-02-11 Thread Thomas Gleixner
On Mon, 11 Feb 2019, Alexandre Chartre wrote: > On 02/10/2019 10:23 PM, Thomas Gleixner wrote: > > 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

Re: [PATCH] x86/alternatives: check int3 breakpoint physical addresses

2019-02-11 Thread Alexandre Chartre
On 02/10/2019 10:23 PM, Thomas Gleixner wrote: 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 som

Re: [PATCH] x86/alternatives: check int3 breakpoint physical addresses

2019-02-10 Thread Thomas Gleixner
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.