Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753846AbbGCKHu (ORCPT ); Fri, 3 Jul 2015 06:07:50 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39365 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753858AbbGCKHm (ORCPT ); Fri, 3 Jul 2015 06:07:42 -0400 Date: Fri, 3 Jul 2015 15:37:39 +0530 From: Pratyush Anand To: linux-kernel@vger.kernel.org Cc: masami.hiramatsu.pt@hitachi.com, dave.long@linaro.org, will.deacon@arm.com Subject: Re: Query: How to blacklist asm symbols for kprobe Message-ID: <20150703100739.GD21990@dhcppc13.redhat.com> References: <20150629091613.GA24236@dhcppc13.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150629091613.GA24236@dhcppc13.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: 716 Lines: 19 On 29/06/2015:02:46:13 PM, Pratyush Anand wrote: > Hi, > > There might be some symbols defined in asm file, which need to be > prevented for kprobe-ing. > > For example, el0_sync, el1_sync, el0_dbg, el1_dbg etc (in > arch/arm64/kernel/entry.S) should be added to the kprobe blacklist > table. How can we do that? I think, we need to define them under "section .entry.text" and then to use arch_within_kprobe_blacklist to prevent such symbols from kprobing. ~Pratyush -- 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/