From: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Anand Je Saipureddy <s.anandje1@gmail.com>,
Clark Williams <williams@redhat.com>,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
cminyard@mvista.com, psiddaiah@mvista.com
Subject: Re: [PATCH] ftrace: Fix improper usage of __trace_stack() function.
Date: Thu, 25 Aug 2022 10:41:36 -0300 [thread overview]
Message-ID: <Ywd8EABDyMywfp7C@uudg.org> (raw)
In-Reply-To: <YuooucgDVO0uDPS/@linutronix.de>
On Wed, Aug 03, 2022 at 09:50:17AM +0200, Sebastian Andrzej Siewior wrote:
> On 2022-07-23 12:19:43 [+0530], Anand Je Saipureddy wrote:
> > In kernel/trace/trace_events_trigger.c --> stacktrace_trigger() -->
> > __trace_stack() is not defined as per the function definition.
> >
> > With commit edbaaa13a660
> > ("tracing: Merge irqflags + preemt counter, add RT bits")
> > the irqflags(flags) and preemption counter(preempt_count()) are
> > now should be evaluated early by tracing_gen_ctx().
> >
> > This patch replaces the irqflags and preemption counter
> > with tracing_gen_ctx().
> >
> > Fixes: 5e8446e3820c ("tracing: Dump stacktrace trigger to the corresponding instance")
> > Signed-off-by: Anand Je Saipureddy <s.anandje1@gmail.com>
> > Reviewed-by: Corey Minyard <cminyard@mvista.com>
>
> Please use [PATCH RT v5.10] in the future.
> Luis, could you please pick it up?
Added to the list.
And thank you for spotting this change, I missed that in my earlier sweep.
Luis
> > ---
> > kernel/trace/trace_events_trigger.c | 8 +++-----
> > 1 file changed, 3 insertions(+), 5 deletions(-)
> >
> > diff --git a/kernel/trace/trace_events_trigger.c b/kernel/trace/trace_events_trigger.c
> > index 75fef9fcfd0f..3c6229f16e81 100644
> > --- a/kernel/trace/trace_events_trigger.c
> > +++ b/kernel/trace/trace_events_trigger.c
> > @@ -1220,12 +1220,10 @@ stacktrace_trigger(struct event_trigger_data *data, void *rec,
> > struct ring_buffer_event *event)
> > {
> > struct trace_event_file *file = data->private_data;
> > - unsigned long flags;
> >
> > - if (file) {
> > - local_save_flags(flags);
> > - __trace_stack(file->tr, STACK_SKIP, preempt_count());
> > - } else
> > + if (file)
> > + __trace_stack(file->tr, tracing_gen_ctx(), STACK_SKIP);
> > + else
> > trace_dump_stack(STACK_SKIP);
> > }
> >
>
> Sebastian
>
---end quoted text---
prev parent reply other threads:[~2022-08-25 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 6:49 Anand Je Saipureddy
2022-08-03 7:50 ` Sebastian Andrzej Siewior
2022-08-25 13:41 ` Luis Claudio R. Goncalves [this message]
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=Ywd8EABDyMywfp7C@uudg.org \
--to=lgoncalv@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=cminyard@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=psiddaiah@mvista.com \
--cc=s.anandje1@gmail.com \
--cc=williams@redhat.com \
/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
all inboxes | Powered by JetHome®