lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 28 Feb 2020 15:13:43 +0100 From: Alexandre Chartre <alexandre.chartre@...cle.com> To: Thomas Gleixner <tglx@...utronix.de>, LKML <linux-kernel@...r.kernel.org> Cc: x86@...nel.org, Steven Rostedt <rostedt@...dmis.org>, Brian Gerst <brgerst@...il.com>, Juergen Gross <jgross@...e.com>, Paolo Bonzini <pbonzini@...hat.com>, Arnd Bergmann <arnd@...db.de> Subject: Re: [patch 07/24] x86/traps: Prepare for using DEFINE_IDTENTRY On 2/25/20 11:16 PM, Thomas Gleixner wrote: > Prepare for using IDTENTRY to define the C exception/trap entry points. It > would be possible to glue this into the existing macro maze, but it's > simpler and better to read at the end to just make them distinct. Provide > a trivial inline helper to read the trap address. > > Signed-off-by: Thomas Gleixner <tglx@...utronix.de> > --- > arch/x86/kernel/traps.c | 5 +++++ > 1 file changed, 5 insertions(+) > > --- a/arch/x86/kernel/traps.c > +++ b/arch/x86/kernel/traps.c > @@ -274,6 +274,11 @@ static void do_error_trap(struct pt_regs > } > } > > +static inline void __user *error_get_trap_addr(struct pt_regs *regs) > +{ > + return (void __user *)uprobe_get_trap_addr(regs); > +} > + > #define IP ((void __user *)uprobe_get_trap_addr(regs)) And you will eventually get rid of this IP macro, right? Reviewed-by: Alexandre Chartre <alexandre.chartre@...cle.com> alex. > #define DO_ERROR(trapnr, signr, sicode, addr, str, name) \ > dotraplinkage void do_##name(struct pt_regs *regs, long error_code) \ > >
Powered by blists - more mailing lists