From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751870Ab2AYOjq (ORCPT ); Wed, 25 Jan 2012 09:39:46 -0500 Received: from mail-wi0-f174.google.com ([209.85.212.174]:37384 "EHLO mail-wi0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750873Ab2AYOjp (ORCPT ); Wed, 25 Jan 2012 09:39:45 -0500 MIME-Version: 1.0 In-Reply-To: <20120110114831.17610.88468.sendpatchset@srdronam.in.ibm.com> References: <20120110114821.17610.9188.sendpatchset@srdronam.in.ibm.com> <20120110114831.17610.88468.sendpatchset@srdronam.in.ibm.com> From: Denys Vlasenko Date: Wed, 25 Jan 2012 15:39:19 +0100 Message-ID: Subject: Re: [PATCH v9 3.2 1/9] uprobes: Install and remove breakpoints. To: Srikar Dronamraju Cc: Peter Zijlstra , Linus Torvalds , Oleg Nesterov , Ingo Molnar , Andrew Morton , LKML , Linux-mm , Andi Kleen , Christoph Hellwig , Steven Rostedt , Roland McGrath , Thomas Gleixner , Masami Hiramatsu , Arnaldo Carvalho de Melo , Anton Arapov , Ananth N Mavinakayanahalli , Jim Keniston , Stephen Rothwell Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 10, 2012 at 12:48 PM, Srikar Dronamraju wrote: > +/* > + * opcodes we'll probably never support: > + * 6c-6d, e4-e5, ec-ed - in > + * 6e-6f, e6-e7, ee-ef - out > + * cc, cd - int3, int I imagine desire to set a breakpoint on int 0x80 will be rather typical. (Same for sysenter). > + * cf - iret Iret does work. Test program for 32-bit x86: /* gcc -nostartfiles -nostdlib -o iret iret.S */ _start: .globl _start pushf push %cs push $_e iret /* will this jump to _e? Yes! */ hlt /* segv if reached */ _e: movl $42, %ebx movl $1, %eax int $0x80 I guess supporting probes in weird stuff like ancient DOS emulators (they actually use iret) is not important. OTOH iret doesn't seem to be too hard: if it fails (bad cs/eflags on stack), then the location of iret instruction per se is not terribly important. If it works, then you need to be careful to not mess up eip, same as you already do with ordinary [l]ret, nothing more. Come to think of it, why do you bother checking for invalid instructions? What can happen if you would just copy and run all instructions? You already are prepared to handle exceptions, right? -- vda