linux-kernel - Re: [PATCH 0/3] ftrace, orc, x86, tracing: Fix stack traces again

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180124075405.33c7a1be@vmware.local.home>
Date:   Wed, 24 Jan 2018 07:54:05 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     linux-kernel@...r.kernel.org,
        Andrew Morton <akpm@...ux-foundation.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        "H. Peter Anvin" <hpa@...or.com>,
        Nikolay Borisov <nborisov@...e.com>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 0/3] ftrace, orc, x86, tracing: Fix stack traces again

On Wed, 24 Jan 2018 05:04:23 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:


> > 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.

Looks to be some kind of anomaly that's not related to these patches.
I wasn't able to reproduce it again. I ran the last 16 tests (test 19 -
34) again, and they all passed. I may investigate that later, as
running without DYNAMIC_FTRACE slows the system down enough to do
strange things all over.

I'll send out the pull request then.

Thanks!

-- Steve