Re: [PATCH 12/19] x86/signal: Land on &frame->retcode when vdso isn't mapped

2020-11-08 Thread Dmitry Safonov
On 11/8/20 7:06 PM, Andy Lutomirski wrote: > On Sat, Nov 7, 2020 at 9:17 PM Dmitry Safonov wrote: >> >> Since commit 9fbbd4dd17d0 ("x86: Don't require the vDSO for handling >> a.out signals") after processing 32-bit signal if there is no vdso >> mapped frame->retcode is used as a landing. >> Do th

Re: [PATCH 12/19] x86/signal: Land on &frame->retcode when vdso isn't mapped

2020-11-08 Thread Andy Lutomirski
On Sat, Nov 7, 2020 at 9:17 PM Dmitry Safonov wrote: > > Since commit 9fbbd4dd17d0 ("x86: Don't require the vDSO for handling > a.out signals") after processing 32-bit signal if there is no vdso > mapped frame->retcode is used as a landing. > Do the same for rt ia32 signals. Am I reading correctl

[PATCH 12/19] x86/signal: Land on &frame->retcode when vdso isn't mapped

2020-11-07 Thread Dmitry Safonov
Since commit 9fbbd4dd17d0 ("x86: Don't require the vDSO for handling a.out signals") after processing 32-bit signal if there is no vdso mapped frame->retcode is used as a landing. Do the same for rt ia32 signals. This shouldn't be mistaken for encouragement for running binaries with executable sta