Re: [PATCH] ptrace: restore the previous single step reporting behavior

On Thu, Jan 28, 2021 at 11:10 AM Linus Torvalds wrote: > You should have pointed to the actual patch. Sorry, I broke the reply threading in my mail client. - Kyle

Re: [PATCH] ptrace: restore the previous single step reporting behavior

On Wed, Jan 27 2021 at 20:55, Gabriel Krisman Bertazi wrote: > Yuxuan Shui writes: > > To gather the right attention, you should directly CC the correct > maintainers. You could have cc'ed them on your reply > Fixes: 64eb35f701f0 ("ptrace: Migrate TIF_SYSCALL_EMU to use SYSCALL_WORK > flag

Re: [PATCH] ptrace: restore the previous single step reporting behavior

Hi, On Wed, Jan 27, 2021 at 11:55 PM Gabriel Krisman Bertazi wrote: > > Yuxuan Shui writes: > > > Commit 64eb35f701f04b30706e21d1b02636b5d31a37d2 changed when single step > > is reported. > > > > Specifically, the report_single_step is changed so that single steps are > > only reported when both

Re: [PATCH] ptrace: restore the previous single step reporting behavior

Yuxuan Shui writes: > Commit 64eb35f701f04b30706e21d1b02636b5d31a37d2 changed when single step > is reported. > > Specifically, the report_single_step is changed so that single steps are > only reported when both SYSCALL_EMU and _TIF_SINGLESTEP are set, while > previously they are reported when _

Re: [PATCH] ptrace: restore the previous single step reporting behavior

Hey everyone, This regression[0] has totally broken rr on 5.11. Could we get someone to look at and merge Yuxuan's patch here? - Kyle [0] https://github.com/rr-debugger/rr/issues/2793

[PATCH] ptrace: restore the previous single step reporting behavior

Commit 64eb35f701f04b30706e21d1b02636b5d31a37d2 changed when single step is reported. Specifically, the report_single_step is changed so that single steps are only reported when both SYSCALL_EMU and _TIF_SINGLESTEP are set, while previously they are reported when _TIF_SINGLESTEP is set without _TI