From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752641AbeAXKEa (ORCPT <rfc822;w@1wt.eu>);
        Wed, 24 Jan 2018 05:04:30 -0500
Received: from mail.kernel.org ([198.145.29.99]:59566 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S932859AbeAXKE2 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 24 Jan 2018 05:04:28 -0500
DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CCC9F20B80
Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org
Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org
Date: Wed, 24 Jan 2018 05:04:23 -0500
From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
        Andrew Morton <akpm@linux-foundation.org>,
        Thomas Gleixner <tglx@linutronix.de>, "H. Peter Anvin" <hpa@zytor.com>,
        Nikolay Borisov <nborisov@suse.com>,
        Josh Poimboeuf <jpoimboe@redhat.com>,
        Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/3] ftrace, orc, x86, tracing: Fix stack traces again
Message-ID: <20180124050423.219260c7@vmware.local.home>
In-Reply-To: <20180124034904.1e5a357b@gandalf.local.home>
References: <20180123183216.191160315@goodmis.org>
        <20180124074649.tuf4imeeerxb6cyb@gmail.com>
        <20180124034904.1e5a357b@gandalf.local.home>
X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 24 Jan 2018 03:49:04 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Wed, 24 Jan 2018 08:46:50 +0100
> Ingo Molnar <mingo@kernel.org> wrote:
> 
>  
> > No fundamental objections from me, assuming they are well tested.
> >  
> 
> Yeah, I ran it through my ftrace test suite, and they did fine till I
> hit test 20 of 34, which tests static ftrace (CONFIG_DYNAMIC_FTRACE not
> set), and it crashed. I'm hoping to have it fixed and retested today.
>

Looking at the crash output, it was hung tasks and not an actual crash.
This is the first time I ran this test on 4.15-rc9, I'll make sure it's
not something associated with rc9 before blaming my patches. With
DYNAMIC_FTRACE disabled, the machine runs much slower. With all the PTI
work, it could possibly pushed it passed a breaking point.

-- Steve