From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753332AbbBSR3V (ORCPT ); Thu, 19 Feb 2015 12:29:21 -0500 Received: from mail-qg0-f52.google.com ([209.85.192.52]:37566 "EHLO mail-qg0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752047AbbBSR3U (ORCPT ); Thu, 19 Feb 2015 12:29:20 -0500 From: Vince Weaver X-Google-Original-From: Vince Weaver Date: Thu, 19 Feb 2015 12:32:41 -0500 (EST) To: Vince Weaver cc: Peter Zijlstra , linux-kernel@vger.kernel.org, Paul Mackerras , Ingo Molnar , Arnaldo Carvalho de Melo , Jiri Olsa , Steven Rostedt Subject: Re: perf: fuzzer gets CPU stuck in perf_callchain() In-Reply-To: Message-ID: References: <20150219165732.GG21418@twins.programming.kicks-ass.net> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 19 Feb 2015, Vince Weaver wrote: > I have to take that back, it turns out the Cortex-A9 machine was wedged > for over a day, I just hadn't noticed because it hadn't dumped any kind > of message about the problem. Hmm. This turns out to be the find_get_context() bug that has been fixed in current git, the kernel I was running wasn't new enough to have the fix in it. So false alarm. Vince