From: David Howells <dhowells@redhat.com>
To: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Cc: dhowells@redhat.com, rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trace: Fix some checker warnings
Date: Mon, 05 Dec 2022 10:22:58 +0000 [thread overview]
Message-ID: <382387.1670235778@warthog.procyon.org.uk> (raw)
In-Reply-To: <20221205180617.9b9d3971cbe06ee536603523@kernel.org>
Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> Could you remove that part from your printf checker macro, and
> apply the below patch?
> Since the printf macros are a kind of improvement but this part is an
> actual bug, need to be fixed on stable kernel too.
Sure. Posted that as v2.
> From 2e993ec80d864677fd42d27f9d4ee01d7e63f8a4 Mon Sep 17 00:00:00 2001
> From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
> Date: Mon, 5 Dec 2022 14:27:00 +0900
> Subject: [PATCH] tracing: Fix complicated dependency of
> CONFIG_TRACER_MAX_TRACE
>
> Both CONFIG_OSNOISE_TRACER and CONFIG_HWLAT_TRACER partially enables the
> CONFIG_TRACER_MAX_TRACE code, but that is complicated and has
> introduced a bug; It declares tracing_max_lat_fops data structure outside
> of #ifdefs, but since it is defined only when CONFIG_TRACER_MAX_TRACE=y
> or CONFIG_HWLAT_TRACER=y, if only CONFIG_OSNOISE_TRACER=y, that
> declaration comes to a definition(!).
>
> To fix this issue, and do not repeat the similar problem, makes
> CONFIG_OSNOISE_TRACER and CONFIG_HWLAT_TRACER enables the
> CONFIG_TRACER_MAX_TRACE always. It has there benefits;
> - Fix the tracing_max_lat_fops bug
> - Simplify the #ifdefs
> - CONFIG_TRACER_MAX_TRACE code is fully enabled, or not.
>
> Fixes: 424b650f35c7 ("tracing: Fix missing osnoise tracer on max_latency")
> Cc: stable@vger.kernel.org
> Reported-by: David Howells <dhowells@redhat.com>
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Tested-by: David Howells <dhowells@redhat.com>
next prev parent reply other threads:[~2022-12-05 10:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 20:07 [PATCH] trace: Fix some checker warnings David Howells
2022-12-02 12:43 ` kernel test robot
2022-12-05 2:22 ` Masami Hiramatsu
2022-12-05 2:39 ` Steven Rostedt
2022-12-05 3:11 ` Masami Hiramatsu
2022-12-05 3:29 ` Steven Rostedt
2022-12-05 3:29 ` Masami Hiramatsu
2022-12-05 3:33 ` Steven Rostedt
2022-12-02 14:24 ` kernel test robot
2022-12-05 3:32 ` Masami Hiramatsu
2022-12-05 8:28 ` David Howells
2022-12-05 9:06 ` Masami Hiramatsu
2022-12-05 10:22 ` David Howells [this message]
2022-12-05 10:29 ` David Howells
2022-12-06 13:59 ` Masami Hiramatsu
2022-12-05 14:40 ` [PATCH] tracing: Fix complicated dependency of kernel test robot
2022-12-05 15:10 ` kernel test robot
2022-12-06 12:56 ` Masami Hiramatsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=382387.1670235778@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox