Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754744AbbGFJD2 (ORCPT ); Mon, 6 Jul 2015 05:03:28 -0400 Received: from foss.arm.com ([217.140.101.70]:58109 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752638AbbGFJD1 (ORCPT ); Mon, 6 Jul 2015 05:03:27 -0400 Date: Mon, 6 Jul 2015 10:03:24 +0100 From: Will Deacon To: Pratyush Anand Cc: "linux-arm-kernel@lists.infradead.org" , "linux@arm.linux.org.uk" , Catalin Marinas , "linux-kernel@vger.kernel.org" , "wcohen@redhat.com" , "dave.long@linaro.org" , "steve.capper@linaro.org" , "masami.hiramatsu.pt@hitachi.com" Subject: Re: [PATCH 1/2] arm64: Blacklist non-kprobe-able symbols Message-ID: <20150706090323.GB30342@arm.com> References: <9994841a0b0a8194a6dcc1b6af148ba358488c62.1436158027.git.panand@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9994841a0b0a8194a6dcc1b6af148ba358488c62.1436158027.git.panand@redhat.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 726 Lines: 17 On Mon, Jul 06, 2015 at 06:03:21AM +0100, Pratyush Anand wrote: > Add all function symbols which are called from do_debug_exception under > NOKPROBE_SYMBOL, as they can not kprobed. It's a shame this has to be so manual, but I suppose it's done on a best-effort basis to catch broken probe placement. If we miss a function and somebody probes it, do we just get stuck in a recursive exception, or could we print something suggesting that a symbol be annotated as NOKPROBE? Will -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/