mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
	linux-trace-kernel@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/4] Revert "tracing: Add "(fault)" name injection to kernel probes"
Date: Sat, 8 Jul 2023 00:46:43 +0900	[thread overview]
Message-ID: <20230708004643.8f6335a2fa682d7dae1f0d0e@kernel.org> (raw)
In-Reply-To: <20230707101420.49b1fd54@gandalf.local.home>

On Fri, 7 Jul 2023 10:14:20 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Fri,  7 Jul 2023 22:41:12 +0900
> "Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> 
> > diff --git a/kernel/trace/trace_probe_kernel.h b/kernel/trace/trace_probe_kernel.h
> > index c4e1d4c03a85..6deae2ce34f8 100644
> > --- a/kernel/trace/trace_probe_kernel.h
> > +++ b/kernel/trace/trace_probe_kernel.h
> > @@ -2,8 +2,6 @@
> >  #ifndef __TRACE_PROBE_KERNEL_H_
> >  #define __TRACE_PROBE_KERNEL_H_
> >  
> > -#define FAULT_STRING "(fault)"
> > -
> 
> Instead of deleting this, why not use it in both places? After applying
> your patch, we have:
> 
>  $ git grep '(fault)' kernel/trace
> kernel/trace/trace_events_synth.c:                      strcpy(str_field, "(fault)");
> kernel/trace/trace_probe.c:             trace_seq_puts(s, "(fault)");
> 
> We could make that consistent with:
> 
> kernel/trace/trace_events_synth.c:                      strcpy(str_field, FAULT_STRING);
> kernel/trace/trace_probe.c:             trace_seq_puts(s, FAULT_STRING);

Indeed. So can I tweak the revert patch more for this?

I would like to move the definition to trace.h.

Thanks,

> 
> -- Steve
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2023-07-07 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 13:40 [PATCH v2 0/4] tracing/probes: Fix bugs in process_fetch_insn Masami Hiramatsu (Google)
2023-07-07 13:40 ` [PATCH v2 1/4] tracing/probes: Fix to avoid double count of the string length on the array Masami Hiramatsu (Google)
2023-07-07 13:41 ` [PATCH v2 2/4] tracing/probes: Fix not to count error code to total length Masami Hiramatsu (Google)
2023-07-07 13:41 ` [PATCH v2 3/4] Revert "tracing: Add "(fault)" name injection to kernel probes" Masami Hiramatsu (Google)
2023-07-07 14:14   ` Steven Rostedt
2023-07-07 15:46     ` Masami Hiramatsu [this message]
2023-07-07 15:48       ` Steven Rostedt
2023-07-08  1:30         ` Masami Hiramatsu
2023-07-07 13:41 ` [PATCH v2 4/4] tracing/probes: Fix to record 0-length data_loc in fetch_store_string*() if fails Masami Hiramatsu (Google)

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=20230708004643.8f6335a2fa682d7dae1f0d0e@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.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

all inboxes | Powered by JetHome®