[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrW7zQMRZOJFVN5AsqMAy=F6jnVyj+QL_w3-xEghqT3XJw@mail.gmail.com>
Date: Sun, 8 Nov 2020 11:06:36 -0800
From: Andy Lutomirski <luto@...nel.org>
To: Dmitry Safonov <dima@...sta.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Dmitry Safonov <0x7f454c46@...il.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Lutomirski <luto@...nel.org>,
Arnd Bergmann <arnd@...db.de>, Borislav Petkov <bp@...en8.de>,
Catalin Marinas <catalin.marinas@....com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Guo Ren <guoren@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
Ingo Molnar <mingo@...hat.com>,
Oleg Nesterov <oleg@...hat.com>,
Russell King <linux@...linux.org.uk>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Thomas Gleixner <tglx@...utronix.de>,
Vincenzo Frascino <vincenzo.frascino@....com>,
Will Deacon <will@...nel.org>, X86 ML <x86@...nel.org>
Subject: Re: [PATCH 12/19] x86/signal: Land on &frame->retcode when vdso isn't mapped
On Sat, Nov 7, 2020 at 9:17 PM Dmitry Safonov <dima@...sta.com> 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 correctly that this makes the ia32 compat signals match
the native ia32 case?
--Andy
Powered by blists - more mailing lists