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: Sun, 17 Nov 2013 16:21:27 +0900 From: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> To: Geert Uytterhoeven <geert@...ux-m68k.org> Cc: Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...nel.org>, Linux-Arch <linux-arch@...r.kernel.org>, Ananth N Mavinakayanahalli <ananth@...ibm.com>, Peter Zijlstra <peterz@...radead.org>, Frederic Weisbecker <fweisbec@...il.com>, the arch/x86 maintainers <x86@...nel.org>, lkml <linux-kernel@...r.kernel.org>, virtualization@...ts.linux-foundation.org, Ingo Molnar <mingo@...hat.com>, Al Viro <viro@...iv.linux.org.uk>, "H. Peter Anvin" <hpa@...or.com>, Thomas Gleixner <tglx@...utronix.de>, Seiji Aguchi <seiji.aguchi@....com>, "David S. Miller" <davem@...emloft.net> Subject: Re: Re: [PATCH -tip RFC v2 01/22] kprobes: Prohibit probing on .entry.text code (2013/11/16 2:46), Geert Uytterhoeven wrote: > On Fri, Nov 15, 2013 at 5:43 PM, Steven Rostedt <rostedt@...dmis.org> wrote: >> On Fri, 15 Nov 2013 04:53:18 +0000 >> Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> wrote: >> >>> .entry.text is a code area which is used for interrupt/syscall >>> entries, and there are many sensitive codes. >>> Thus, it is better to prohibit probing on all of such codes >>> instead of a part of that. >>> Since some symbols are already registered on kprobe blacklist, >>> this also removes them from the blacklist. >> >> This change only works with x86. On other archs, I get this: >> >> kernel/built-in.o: In function `register_kprobe': >> (.kprobes.text+0x9f4): undefined reference to `__entry_text_start' >> kernel/built-in.o: In function `register_kprobe': >> (.kprobes.text+0x9f8): undefined reference to `__entry_text_end' >> make[1]: *** [vmlinux] Error 1 >> make: *** [sub-make] Error 2 > > X86 is the sole architecture that has ENTRY_TEXT in its > arch/*/kernel/vmlinux.lds.S. Ah, thanks! I'll fix that. BTW, should I add CONFIG_HAVE_ENTRY_TEXT for x86 and use it or just use CONFIG_X86 to detect it? Thank you, -- Masami HIRAMATSU IT Management Research Dept. Linux Technology Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: masami.hiramatsu.pt@...achi.com -- 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