Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757137AbaLINd6 (ORCPT ); Tue, 9 Dec 2014 08:33:58 -0500 Received: from mail-wi0-f169.google.com ([209.85.212.169]:38336 "EHLO mail-wi0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757070AbaLINdy (ORCPT ); Tue, 9 Dec 2014 08:33:54 -0500 Date: Tue, 9 Dec 2014 13:33:42 +0000 From: Steve Capper To: Masami Hiramatsu Cc: David Long , "Jon Medhurst (Tixy)" , Russell King , Ananth N Mavinakayanahalli , Sandeepa Prabhu , Catalin Marinas , Will Deacon , "linux-kernel@vger.kernel.org" , Anil S Keshavamurthy , William Cohen , David Miller , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH v3 0/5] ARM64: Add kernel probes(Kprobes) support Message-ID: <20141209133340.GA20265@linaro.org> References: <547C36DB.7060903@hitachi.com> <547F242D.1060705@redhat.com> <547F94B0.1000902@linaro.org> <547FB5DD.901@redhat.com> <547FCB73.1010707@linaro.org> <54803ADD.2090201@hitachi.com> <54804B1F.3020703@hitachi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54804B1F.3020703@hitachi.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 04, 2014 at 08:53:03PM +0900, Masami Hiramatsu wrote: > (2014/12/04 20:29), Steve Capper wrote: > > >> I'd like to ask you to try my fix on your machine, with my reproducing > >> methods. (do not use sytemtap nor perf, those can have other issues) > >> > > > > Thank you Masami, > > > > I tried the following commands: > > > > echo "p:trace_event_buffer_lock_reserve > > trace_event_buffer_lock_reserve" > > > /sys/kernel/debug/tracing/kprobe_events > > echo 1 > /sys/kernel/debug/tracing/events/kprobes/enable > > echo 1 > /sys/kernel/debug/tracing/events/sched/sched_process_exec/enable > > > > The system appeared okay, I then cat'ed out: > > # cat /sys/kernel/debug/tracing/kprobe_profile > > trace_event_buffer_lock_reserve 25 25 > > > > I got similar output (i.e. no crashes) both with and without the > > interrupt fix you recommended. > > > > I'm not sure how to interpret this, please let me know if you would > > like me to run any other tests? > > > > (I did also try your proposed fix with perf + memcpy and that crashed > > in a similar way as before). > > Hmm, then the bug is still there, and the bug may not be in the recursive > call path... We need to find another suspicious code in the patch. > Not sure if this is helpful, but the following also caused a crash for me: echo "p:trace_event_buffer_lock_reserve trace_event_buffer_lock_reserve" > /sys/kernel/debug/tracing/kprobe_events echo "p:memcpy memcpy" >> /sys/kernel/debug/tracing/kprobe_events echo 1 > /sys/kernel/debug/tracing/events/kprobes/enable [immediate crash] The crash point for me is in the arm64 ASID allocator, it again looks like the interrupts are in an unexpected state. (check_and_switch_context goes down the irqs disabled code path, I think incorrectly). This occurred for me both with and without the proposed irq saving fix. I will do some more digging. Cheers, -- Steve -- 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/