Sergei Shtylyov wrote:
> Hello.
>
> Jason Wessel wrote:
>
>> I finally came across the case where CONFIG_DEBUG_PREEMPT crashes
>> user space processes on i386 and x86_64. When debugging a syscall,
>> if gdb reads any invalid memory and triggers the may_fault path, the
>> preempt count is not r
Hello.
Jason Wessel wrote:
> I finally came across the case where CONFIG_DEBUG_PREEMPT crashes user
> space processes on i386 and x86_64. When debugging a syscall, if gdb
> reads any invalid memory and triggers the may_fault path, the preempt
> count is not restored when doing the context re
I finally came across the case where CONFIG_DEBUG_PREEMPT crashes user
space processes on i386 and x86_64. When debugging a syscall, if gdb
reads any invalid memory and triggers the may_fault path, the preempt
count is not restored when doing the context restore.
The simple fix is to decre
