From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755304Ab1KWUwp (ORCPT ); Wed, 23 Nov 2011 15:52:45 -0500 Received: from casper.infradead.org ([85.118.1.10]:60325 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755145Ab1KWUwo convert rfc822-to-8bit (ORCPT ); Wed, 23 Nov 2011 15:52:44 -0500 Message-ID: <1322081530.14799.97.camel@twins> Subject: Re: [PATCH v7 3.2-rc2 5/30] uprobes: copy of the original instruction. From: Peter Zijlstra To: Steven Rostedt Cc: Srikar Dronamraju , Linus Torvalds , Oleg Nesterov , Andrew Morton , LKML , Linux-mm , Ingo Molnar , Andi Kleen , Christoph Hellwig , Roland McGrath , Thomas Gleixner , Masami Hiramatsu , Arnaldo Carvalho de Melo , Anton Arapov , Ananth N Mavinakayanahalli , Jim Keniston , Stephen Wilson Date: Wed, 23 Nov 2011 21:52:10 +0100 In-Reply-To: <1322077748.20742.68.camel@frodo> References: <20111118110631.10512.73274.sendpatchset@srdronam.in.ibm.com> <20111118110733.10512.11835.sendpatchset@srdronam.in.ibm.com> <1322073616.14799.96.camel@twins> <1322077748.20742.68.camel@frodo> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT X-Mailer: Evolution 3.2.1- Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2011-11-23 at 14:49 -0500, Steven Rostedt wrote: > On Wed, 2011-11-23 at 19:40 +0100, Peter Zijlstra wrote: > > On Fri, 2011-11-18 at 16:37 +0530, Srikar Dronamraju wrote: > > > + /* TODO : Analysis and verification of instruction */ > > > > As in refuse to set a breakpoint on an instruction we can't deal with? > > > > Do we care? The worst case we'll crash the program, but if we're allowed > > setting uprobes we already have enough privileges to do that anyway, > > right? > > Well, I wouldn't be happy if I was running a server, and needed to > analyze something it was doing, and because I screwed up the location of > my probe, I crash the server, made lots of people unhappy and lose my > job over it. > > I think we do care, but it can be a TODO item. But but but, why not let userspace sort it? And if you're going to provide the kernel with inode:offset data yourself, you're already well aware of wtf you're doing.