| 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
| ||
|
Message-ID: <863e9df20801270733n4b82b595u8421fb07c18acaa6@mail.gmail.com> Date: Sun, 27 Jan 2008 21:03:58 +0530 From: "Abhishek Sagar" <sagar.abhishek@...il.com> To: "Masami Hiramatsu" <mhiramat@...hat.com> Cc: LKML <linux-kernel@...r.kernel.org>, jkenisto@...ibm.com, ananth@...ibm.com, "Ingo Molnar" <mingo@...e.hu> Subject: Re: [PATCH 3/3] x86: WARN_ON breakpoints from .kprobes.text section On 1/27/08, Masami Hiramatsu <mhiramat@...hat.com> wrote: > Sorry, I can not understand what issue these patches can solve. > The breakpoint which is inserted by external debugger will be checked by > kprobe_handler() and be passed to other exception_notify_handlers. > In that case, we don't need to warn it. > I think current code is enough simple. kprobe_handler has a blanket check for all non-kprobe breakpoints. They're all left to the kernel to handle. This is fine. Although external debuggers are free to plant breakpoints anywhere, they should be discouraged from doing so inside .kprobes.text region. Placing them there may lead to recursive page-fault/trap handling. It's a defensive check. I hope I've been able to clarify. > -- > Masami Hiramatsu > > Software Engineer > Hitachi Computer Products (America) Inc. > Software Solutions Division > > e-mail: mhiramat@...hat.com Thanks, Abhishek Sagar -- 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