Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 9 Mar 2022 11:31:47 -0500
From:   Steven Rostedt <rostedt@goodmis.org>
To:     Daniel Bristot de Oliveira <bristot@kernel.org>
Cc:     Nicolas Saenz Julienne <nsaenzju@redhat.com>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        linux-trace-devel@vger.kernel.org, mtosatti <mtosatti@redhat.com>
Subject: Re: Warning when exiting osnoise tracer
Message-ID: <20220309113147.7a8d59c6@gandalf.local.home>
In-Reply-To: <20220309105403.66d2b6ef@gandalf.local.home>
References: <c898d1911f7f9303b7e14726e7cc9678fbfb4a0e.camel@redhat.com>
        <eeb95928-02cf-a38c-8079-d2bbf4edb7e7@kernel.org>
        <20220309105403.66d2b6ef@gandalf.local.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Wed, 9 Mar 2022 10:54:03 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:

> lot of noise to dmesg, I can easily miss warnings there. I'll add a test to
> look for Call Traces at the end of the test.

My tests now detect this :-)

I tried it out on the current kernel, and it now gives me a failure if one
of the tests trigger a WARN_ON in the kernel. Which the test that runs a
record against every tracer, including osnoise, just failed on.

-- Steve