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: Tue, 13 Mar 2012 14:54:33 +0530 From: Srikar Dronamraju <srikar@...ux.vnet.ibm.com> To: Ingo Molnar <mingo@...e.hu> Cc: "H. Peter Anvin" <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Oleg Nesterov <oleg@...hat.com>, LKML <linux-kernel@...r.kernel.org>, Christoph Hellwig <hch@...radead.org>, Steven Rostedt <rostedt@...dmis.org>, Thomas Gleixner <tglx@...utronix.de>, Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>, Anton Arapov <anton@...hat.com>, Ananth N Mavinakayanahalli <ananth@...ibm.com>, Jim Keniston <jkenisto@...ux.vnet.ibm.com>, Jiri Olsa <jolsa@...hat.com>, Josh Stone <jistone@...hat.com> Subject: Re: [PATCH] uprobes/core: handle breakpoint and signal step exception. * Ingo Molnar <mingo@...e.hu> [2012-03-13 06:47:44]: > > * Ingo Molnar <mingo@...e.hu> wrote: > > > To make it available to uprobes please move is_ia32_task() to > > processor.h and make it return 1 on i386 kernels. This should > > be a very simple patch - and that's all that is needed. > > Side note: in general I don't mind making compat.h a bit more > generic (at all), but is_ia32_task() is really a generic x86 > specific check that we can move to processor.h cleanly. > > Some other effort should make compat.h bitness agnostic - > uprobes doesn't actually make use of the compat types and > facilities there, and it resulted in a nonsensical change like > making the alloc function generic ... > Okay, Will move is_ia32_task() to processor.h and use it. -- Thanks and Regards Srikar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists